From: | Darcy Buskermolen <darcyb(at)commandprompt(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Simple thing to make pg_autovacuum more useful |
Date: | 2008-01-18 15:53:37 |
Message-ID: | 200801180753.37788.darcyb@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thursday 17 January 2008 19:17:00 Joshua D. Drake wrote:
> On Thu, 17 Jan 2008 21:43:46 -0300
>
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > Tom Lane wrote:
> > > Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > > > All this thread is a waste of time. We've previously agreed that
> > > > we're going to store autovacuum per-table settings in
> > > > pg_class.reloptions.
> > >
> > > I had forgotten that discussion. So the plan is for the
> > > pg_autovacuum catalog to go away entirely, correct?
> >
> > Yup.
>
> Wait .reloptions is a column... how are we going to populate it and
> array?
ALTER TABLE foo SET autovacuum to true;
ALTER TABLE foo SET autovacuum_naptime to '1min';
(or there about)
I suppose we could also have pg_autovacuum become a view, with rules to manage
relopts.
>
> Sincerely,
>
> Joshua D. Drake
--
Darcy Buskermolen
Command Prompt, Inc.
+1.503.667.4564 X 102
http://www.commandprompt.com/
PostgreSQL solutions since 1997
From | Date | Subject | |
---|---|---|---|
Next Message | Maciej Grygorcewicz | 2008-01-18 18:30:41 | Problem with correct compiling and linking server side C function on Windows ,c++ Builder |
Previous Message | Jonah H. Harris | 2008-01-18 13:10:01 | Re: modularity of PostgreSQL |