From: Chris Browne <cbbrowne@acm.org>
To: pgsql-hackers@postgresql.org
Subject: Re: autovacuum
Date: Wed, 01 Feb 2006 12:54:42 -0500
Message-ID: <60lkwvklr1.fsf@dba2.int.libertyrms.com> (raw)
References: <1137992841.28304.48.camel@localhost.localdomain>
<5001.71.40.140.99.1138286468.squirrel@mail.tocr.com>
<60psm7knlq.fsf@dba2.int.libertyrms.com>
<20060201172905.GA7879@surnet.cl>
alvherre@alvh.no-ip.org (Alvaro Herrera) writes:
> Chris Browne wrote:
>
>> It strikes me as a slick idea for autovacuum to take on that
>> behaviour. If the daily backup runs for 2h, then it is quite futile
>> to bother vacuuming a table multiple times during that 2h period when
>> none of the tuples obsoleted during the 2h period will be able to be
>> cleaned out until the end.
>
> Hmm, yeah, sounds useful. There's one implementation issue to notice
> however, and it's that the autovacuum process dies and restarts for each
> iteration, so there's no way for it to remember previous state unless
> it's saved somewhere permanent, as the stats info is.
Hmm. It restarts repeatedly??? Hmmm...
> However this seems at least slightly redundant with the "maintenance
> window" feature -- you could set a high barrier to vacuum during the
> daily backup period instead. (Anybody up for doing this job?)
In effect, this would be an alternative to the "window" feature. You
open the window by starting pg_dump; pg_autovacuum would automatically
notice that as the eldest XID, and stop work until the pg_dump
actually finished.
In a way, it strikes me as more elegant; it would automatically notice
"backup windows," noticing *exact* start and end times...
--
select 'cbbrowne' || '@' || 'ntlug.org';
http://www.ntlug.org/~cbbrowne/linuxxian.html
"I'm sorry, Mr. Kipling, but you just don't know how to use the
English Language." -- Editor of the San Francisco Examiner, informing
Rudyard Kipling, who had one article published in the newspaper, that
he needn't bother submitting a second, 1889
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-admin@postgresql.org
Cc: cbbrowne@acm.org, pgsql-hackers@postgresql.org
Subject: Re: autovacuum
In-Reply-To: <60lkwvklr1.fsf@dba2.int.libertyrms.com>
* 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