Gregory Stark wrote:
> "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
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
- 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.
In response to
pgsql-hackers by date
|Next:||From: Teodor Sigaev||Date: 2006-12-21 18:46:25|
|Subject: Re: tsearch in core patch, for review|
|Previous:||From: Teodor Sigaev||Date: 2006-12-21 18:29:30|
|Subject: Re: [HACKERS] Bundle of patches|