On 8/21/07, Sachchida Ojha <sojha@secure-elements.com> wrote:
> vacuum_cost_delay = 200
> vacuum_cost_page_hit = 1
> vacuum_cost_page_miss = 10
> vacuum_cost_page_dirty = 20
> vacuum_cost_limit = 200
>
> autovacuum = on
> autovacuum_naptime = 3600
>
> maintenance_work_mem = 256MB # min 1024, size
That's a REALLY long naptime. Better to let autovacuum decide if you
need vacuum more often, and just increase the vacuum_cost_delay and
decrease vacuum_cost_limit so that vacuum doesn't slam your I/O.
Maintenance work mem on the other hand is plenty big. and your fsm
settings seem large enough to handle your freed space.
But making vacuum wait so long between runs may be slowly bloating
your data store, and then vacuum becomes more and more expensive
because it takes longer and longer to run.