Re: Simple thing to make pg_autovacuum more useful - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Simple thing to make pg_autovacuum more useful
Date
Msg-id 20080118082326.GA7353@svr2.hagander.net
Whole thread Raw
In response to Re: Simple thing to make pg_autovacuum more useful  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
On Fri, Jan 18, 2008 at 01:07:27AM +0000, Gregory Stark wrote:
> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
> 
> > "Joshua D. Drake" <jd@commandprompt.com> writes:
> >> You are offering what appears to be a "solution". A perfectly valid one
> >> in fact. Which one is going to get done first? Which one is going to
> >> provide immediate benefit? 
> >
> > The problem is that your "immediate benefit" is to encourage people
> > to do direct manual insertions into pg_autovacuum, which is something
> > that we shouldn't be encouraging, because it's not the correct long-term
> > solution.  Or even short-term --- it seems reasonably likely to me that
> > something could be done about building a decent API in the 8.4 cycle,
> > which is the soonest we could entertain a proposal to put defaults on
> > pg_autovacuum anyway.
> 
> Are you picturing adding ALTER TABLE commands to set autovacuum parameters? Or
> do you mean for tools like pgadmin to control this? Because the latter could
> happen even during the 8.3 cycle (though I perhaps not with pgadmin itself
> which I think follows the Postgres release cycle).

Of course, pgadmin already does this :-P Ask that tall guy sitting next to
you for a demo...

What it doesn't do is help you figure out what values to put in...

//Magnus


pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: Declarative partitioning grammar
Next
From: "Dave Page"
Date:
Subject: Re: Simple thing to make pg_autovacuum more useful