| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Jim Nasby <jim(dot)nasby(at)enterprisedb(dot)com>, "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 15:57:34 |
| Message-ID: | 458AAEEE.1000003@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?)
>
Yes, it adds/removes/edits rows in pg_autovacuum as required.
Regards, Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2006-12-21 16:05:16 | pgsql: Initial SQL/XML support: xml data type and initial set of |
| Previous Message | Stephen Frost | 2006-12-21 15:52:46 | Re: ERROR: tuple concurrently updated |