Re: [ADMIN] autovacuum on a -mostly- r/o table
- From: Tobias Brox <tobias(at)nordicbet(dot)com>
- To: "Matthew T. O'Connor" <matthew(at)zeut(dot)net>
- Cc: Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Edoardo Ceccarelli <eddy(at)axa(dot)it>, postgres performance list <pgsql-performance(at)postgresql(dot)org>, pgsql-admin(at)postgresql(dot)org
- Subject: Re: [ADMIN] autovacuum on a -mostly- r/o table
- Date: Sun, 15 Oct 2006 11:52:59 +0200
- Message-id: <20061015095259(dot)GA24002(at)oppetid(dot)no>
[Matthew T. O'Connor - Wed at 02:33:10PM -0400]
> In addition autovacuum respects the work of manual or cron based
> vacuums, so if you issue a vacuum right after a daily batch insert /
> update, autovacuum won't repeat the work of that manual vacuum.
I was experimenting a bit with autovacuum now. To make the least effect
possible, I started with a too high cost_delay/cost_limit-ratio. The
effect of this was that autovacuum "never" finished the transactions it
started with, and this was actually causing the nightly vacuum to not do
it's job good enough.
Home |
Main Index |
Thread Index