Olleg Samoylov <[EMAIL PROTECTED]> writes:
> IMHO "vacuumdb -a" must don't vacuum database with
> datvacuumxid=datfrozenxid.
That's not going to work because it will fail to detect whether the
database has been modified since the VACUUM FREEZE command.
In any case, what's the point? As long as you have a routine vacuuming
process in place, it doesn't really matter whether template1 gets
scanned. The only reason VACUUM FREEZE exists at all is to make it
possible to have a non-connectable, non-vacuumable template0.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
