Peter Eisentraut <peter_e@gmx.net> writes:
> Benjamin Krajmalnik wrote:
>> What can be causing this growth? Not vacuuming often enough?
> The is exactly the reason.
>> I hav
>> pg_autovacuum running every 60 seconds. These tables have 10-15
>> insert/update statements per second.
> You should probably run VACUUM FULL to get the table back to a normal
> size and then closely monitor what pg_autovacuum actually does.
CLUSTER might be a better answer, since VACUUM FULL won't do anything
to help shrink the indexes.
As for the pg_autovacuum frequency, realize that pg_autovacuum processes
one database per firing. So if you have N databases, any one database
is going to be looked at every N*60 seconds, not every 60 seconds.
You might need a shorter autovacuum cycle.
Lastly, what PG version is this? We had some bugs that kept autovacuum
from being fully informed in some cases, but AFAIK they're all fixed in
the latest minor releases.
regards, tom lane
