> Did you use -f on the vacuumdb? If not, it did a normal vacuum (which
> isn't likely to help) not a full vacuum.
There are scenarios where VACUUM FULL is not an option because
of its resource-hungriness and plain VACUUM just doesn't seem
We have a production database that happens to receive several
thousand row updates per minute. We VACUUM ANALYZE every four
hours with max_fsm_pages set to 2100000, and it's no use.
The only way to prevent the system from filling up the data
partition seems to be to regularly schedule downtime to dump
and restore the whole db (the dump is ~150 MiB gzipped).
Tomas Szepe <szepe(at)pinerecords(dot)com>
In response to
pgsql-bugs by date
|Next:||From: Stephan Szabo||Date: 2003-09-26 18:25:15|
|Subject: Re: Postgresql 'eats' all mi data partition|
|Previous:||From: Bruce Momjian||Date: 2003-09-26 17:52:18|
|Subject: Re: pg_dump/all doesn't output schemas correctly (v7.3.4)|