| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Jim Nasby" <jim(dot)nasby(at)enterprisedb(dot)com>, "Dave Page" <dpage(at)postgresql(dot)org> |
| Cc: | "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:04:43 |
| Message-ID: | 1166713483.3783.66.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | JEAN-PIERRE PELLETIER | 2006-12-21 15:10:07 | log_min_error_statement and parameters value |
| Previous Message | Simon Riggs | 2006-12-21 14:56:30 | Re: Tuning single row operations |