Re: pg_autovacuum next steps - Mailing list pgsql-hackers

From Alex J. Avriette
Subject Re: pg_autovacuum next steps
Date
Msg-id 20040322194441.GJ25451@posixnap.net
Whole thread Raw
In response to pg_autovacuum next steps  ("Matthew T. O'Connor" <matthew@zeut.net>)
Responses Re: pg_autovacuum next steps
List pgsql-hackers
On Sun, Mar 21, 2004 at 05:32:59PM -0500, Matthew T. O'Connor wrote:
> Lately I have been thinking about the next steps for the pg_autovacuum
> daemon.  I have written up a document that describes what I'm planning
> to do next.   Please read the attached and response as I would really
> like some feedback.

Hi, Matthew. For our uses, we found that pg_autovacuum did not behave
as expected with vacuum_threshold set to 0.  For our purposes, we have
a very good idea of how many tuples need to be slurped up over a given
interval, and would like the autovacuum daemon to simply go through and
vacuum when it hits a, er, threshold.

Obligatory explanation: We were doing this with cron, but when
something gets really ugly, cron is not as intuitive as autovacuum.

Having this in the postmaster would be fine by me (and in fact, I would
even suggest that it belongs there), but I really need to have more
flexibility or we are going to (read: I will be tasked with) be writing
our own.

Sorry for the terseness -- and I haven't had a chance to go over the
whole thread; we're moving from 7.3.2 to 7.4.2 on "the big database" 
this week.

Alex

--
alex@posixnap.net
Alex J. Avriette, Systems Programmer
"You have a spell checker. It is called a brain. Please use it." - Chris Lyth


pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use
Next
From: Bernd Helmle
Date:
Subject: Thoughts about updateable views