Currently postgresql's "vacuum full" also locks the affected tables.
Does 8.3 vacuum full effectively make a copy of the entire table? How
much extra space will the various vacuums use while vacuuming?
As to 8.3 and how it handles vacuum-full internally, I can't say for
certain without reading the notes. I suspect it is an in-place operation
similar to prior versions.
But if you are running PG 7.0 or later (maybe even earlier, I didn't
look) and have enough disk space to replicate the table, you can use
CLUSTER to do a copy-to-new file and delete old file operation. It does
still lock the table and it does require that the table have an index
based on which it will physically reorder the table but it is usually
_way_ faster and you get fresh indexes as a bonus.
IOW, PG offers you the choice to pick whichever is best for you.
Cheers,
Steve
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
