[no subject]

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]=20
> Sent: Sunday, July 23, 2006 11:48 AM
> To: Peter Eisentraut
> Cc: pgsql-admin(at)postgresql(dot)org; Benjamin Krajmalnik
> Subject: Re: [ADMIN] Unexplained growth of tables=20
>=20
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Benjamin Krajmalnik wrote:
> >> What can be causing this growth?  Not vacuuming often enough?
>=20
> > The is exactly the reason.
>=20
> >> I hav
> >> pg_autovacuum running every 60 seconds.  These tables have 10-15=20
> >> insert/update statements per second.
>=20
> > You should probably run VACUUM FULL to get the table back=20
> to a normal=20
> > size and then closely monitor what pg_autovacuum actually does.
>=20
> CLUSTER might be a better answer, since VACUUM FULL won't do=20
> anything to help shrink the indexes.
>=20
> As for the pg_autovacuum frequency, realize that=20
> pg_autovacuum processes one database per firing.  So if you=20
> have N databases, any one database is going to be looked at=20
> every N*60 seconds, not every 60 seconds.
> You might need a shorter autovacuum cycle.
>=20
> Lastly, what PG version is this?  We had some bugs that kept=20
> autovacuum from being fully informed in some cases, but AFAIK=20
> they're all fixed in the latest minor releases.
>=20
> 			regards, tom lane
>=20