"Jim Nasby" <jim(dot)nasby(at)enterprisedb(dot)com> 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
Sometimes the parser can look ahead to the next keyword to determine which
production to use but usually you're best off just looking for a grammatical
construct that doesn't look ambiguous even to a naive human reader.
In response to
pgsql-hackers by date
|Next:||From: Teodor Sigaev||Date: 2006-12-21 18:24:49|
|Subject: Re: pgsql: Initial SQL/XML support: xml data type and|
|Previous:||From: Jim Nasby||Date: 2006-12-21 18:10:08|
|Subject: Re: Interface for pg_autovacuum|