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 [EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
