From: Matthew T. O'Connor <matthew@zeut.net>
To: Tobias Brox <tobias@nordicbet.com>
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 10:42:34 -0400
Message-ID: <453248DA.7050806@zeut.net> (raw)
In-Reply-To: <20061015095259.GA24002@oppetid.no>
References: <20061015095259.GA24002@oppetid.no>
Tobias Brox wrote:
> [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.
Yeah, I think if the delay settings are too high it can cause problems,
that's part of the reason we have yet to turn these on be default since
we won't have enough data to suggest good values. Can you tell us what
settings you finally settled on?
BTW hopefully for 8.3 we are going to add the concept of maintenance
windows to autovacuum, during these periods you can lower the thresholds
and perhaps even change the delay settings to make autovacuum more
aggressive during the maintenance window. This hopefully will just
about eliminate the need for nightly cron based vacuum runs.
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: matthew@zeut.net, tobias@nordicbet.com, nagy@ecircle-ag.com, eddy@axa.it, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
In-Reply-To: <453248DA.7050806@zeut.net>
* 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