Vacuum full is kind of a drag, if most of the tuples have been deleted.
In fact, it is faster for me to dump, drop, and recreate my databases than
it is to vacuum full.
It would be nice if vacuum full had logic that understood when a table has
4000 tuples and 4000000000 deleted tuples it will probably be a lot faster
to just copy the good tuples into a new table and unlink the old table.
Does anyone know the effect of vacuum_mem setting on vacuum full time?
Mine is currently the default setting of 8192 (KB presumably). My
databases are 70GB on a machine with 2GB main memory.
-jwb