Re: Simple thing to make pg_autovacuum more useful

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Simple thing to make pg_autovacuum more useful
Date: 2008-01-18 01:07:27
Message-ID: 87odbkc568.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> "Joshua D. Drake" <jd(at)commandprompt(dot)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).

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-01-18 01:34:07 Re: Simple thing to make pg_autovacuum more useful
Previous Message Alvaro Herrera 2008-01-18 00:47:26 Re: [HACKERS] SSL over Unix-domain sockets