Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] autovacuum

From: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
To: Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] autovacuum
Date: 2006-02-01 17:43:32
Message-ID: 43E0F344.5020008@zeut.net (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-hackers
Alvaro Herrera wrote:
> 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.
> 
> 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?)

I can't promise anything, but it's on my list of things to hopefully 
find time for in the coming months.  No way I can start it in Feb, but 
maybe sometime in March.  Anyone else?


Matt

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-02-01 17:45:11
Subject: Re: TODO-Item: B-tree fillfactor control
Previous:From: Alvaro HerreraDate: 2006-02-01 17:29:05
Subject: Re: [HACKERS] autovacuum

pgsql-admin by date

Next:From: Chris BrowneDate: 2006-02-01 17:54:42
Subject: Re: autovacuum
Previous:From: Alvaro HerreraDate: 2006-02-01 17:29:05
Subject: Re: [HACKERS] autovacuum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group