Gregory Stark wrote:
"Jim Nasby" <[EMAIL PROTECTED]> writes:
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?
The way to predict when you're going to run into conflicts in a case like this
is to ask what happens if you have a column named "autovacuum" or
"autoanalyze"...
Might it not be cleaner to treat them as scoped configuration values?
ALTER TABLE foo SET autovacuum.threshold = ...
Presumably it's not going to be the last such setting, and would give
you a common format for setting all manner of system-object related things:
- column statistics
- fill-factor
- comment
- per-column locale (when we get it)
- any module-related tuning (tsearch2? slony?)
That way the parser just needs to treat the next thing after "SET" as a
(possibly compound) identifier.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
