From: Tobias Brox <tobias@nordicbet.com>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: Csaba Nagy <nagy@ecircle-ag.com>
Cc: Edoardo Ceccarelli <eddy@axa.it>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
Date: Sun, 15 Oct 2006 11:52:59 +0200
Message-ID: <20061015095259.GA24002@oppetid.no> (raw)
[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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tobias@nordicbet.com, matthew@zeut.net, nagy@ecircle-ag.com, eddy@axa.it, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
In-Reply-To: <20061015095259.GA24002@oppetid.no>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox