>>>>> "MvO" == Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
MvO> I'd suggest, use the autovacuum daemon, tune your FSM settings to what
MvO> you expect the load to be and maybe schedule a database-wide
MvO> REINDEX/VACUUM FULL regularly. We found doing it once a month was
MvO> enough to keep it tip-top over the long term...
If you know your application usage patterns well, scheduling vacuum
via cron probably would be better than autovacuum. autovacuum runs
whenever it pleases, and doesn't deal well with extremely large tables
(ie, it never runs vacuum on them since the % change may be small even
though millions of rows are "expired"). You can even vacuum differnt
tables on different schedules. Just make sure the VACUUMs don't
I haven't run reindex or vacuum full since I upgraded to 7.4.x. The
indexes are not bloating, and sufficient calls to vacuum keep the
"stable set size" of the db pretty constant. ie, it doesn't grow
without bounds, as the OP fears.
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
In response to
pgsql-general by date
|Next:||From: Joachim Zobel||Date: 2004-12-28 15:05:53|
|Subject: Re: Get current trasanction id|
|Previous:||From: Nefnifi, Kasem||Date: 2004-12-28 14:44:56|
|Subject: Re: running a query file of 42MB|