Christopher Browne <cbbrowne@acm.org> writes:
> Not vacuuming for four months was a severe error, which means that you
> now need to run a really full maintenance cycle. At the next possible
> opportunity, you really need to do a VACUUM FULL on the whole
> database.
Dump, initdb, reload would very likely be less painful ...
Something that hasn't ever been very clearly documented is that the
VACUUM FULL mechanism is designed for compacting out relatively small
amounts of dead space, like maybe 10-20%. When you've got a table
that's got so much dead space that VACUUM FULL is going to move nearly
all the live rows, the proposition is a loser. CLUSTER or dump/reload
will be better, because those approaches don't bother to try to maintain
the existing indexes incrementally: they throw away the indexes and
start from scratch.
regards, tom lane
