Tom Lane wrote:
"Olleg Samoylov" <[EMAIL PROTECTED]> writes:
Opps, template1 must not be vacuumed.
Says who?
If we didn't vacuum template1 then it would be subject to XID
wraparound problems, unless it had never been modified, which is
something vacuumdb can't count on.
template1 frozen by "vacuum freeze", thus can't be subject of XID
wraparound problems, isn't it?
man vacuum:
If this is done when there are no other open transactions in the same
database, then it is guaranteed that all tuples in the
database are ‘‘frozen’’ and will not be subject to transaction
ID wraparound problems, no matter how long the database is left
unvacuumed.
IMHO "vacuumdb -a" must don't vacuum database with
datvacuumxid=datfrozenxid.
--
Olleg Samoylov
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
