From: | "Jim Nasby" <jim(dot)nasby(at)enterprisedb(dot)com> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Cc: | "Dave Page" <dpage(at)postgresql(dot)org>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Interface for pg_autovacuum |
Date: | 2006-12-21 18:10:08 |
Message-ID: | 7C4D872D-7172-40AA-8104-A5AE4241048E@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
How about...
ALTER TABLE ...
ALTER AUTOVACUUM [ THRESHOLD | SCALE | COST DELAY | COST LIMIT ]
ALTER AUTOANALYZE [ THRESHOLD | SCALE ]
... or would that create a whole bunch of reserved words?
On Dec 21, 2006, at 10:04 AM, Simon Riggs wrote:
> On Wed, 2006-12-20 at 09:47 -0500, Jim Nasby wrote:
>
>> On the other hand, this would be the only part of the system where
>> the official interface/API is a system catalog table. Do we really
>> want to expose the internal representation of something as our API?
>> That doesn't seem wise to me...
>
> Define and agree the API (the hard bit) and I'll code it (the easy
> bit).
>
> We may as well have something on the table, even if it changes later.
>
> Dave: How does PgAdmin handle setting table-specific autovacuum
> parameters? (Does it?)
>
> --
> Simon Riggs
> EnterpriseDB http://www.enterprisedb.com
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>
--
Jim Nasby jim(dot)nasby(at)enterprisedb(dot)com
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2006-12-21 18:20:41 | Re: Interface for pg_autovacuum |
Previous Message | Alvaro Herrera | 2006-12-21 17:41:32 | Re: Autovacuum Improvements |