Skip site navigation (1) Skip section navigation (2)

Re: Interface for pg_autovacuum

From: Richard Huxton <dev(at)archonet(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Jim Nasby <jim(dot)nasby(at)enterprisedb(dot)com>,Simon Riggs <simon(at)2ndquadrant(dot)com>,Dave Page <dpage(at)postgresql(dot)org>, "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 18:37:02
Message-ID: 458AD44E.2070708@archonet.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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
> "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

In response to

pgsql-hackers by date

Next:From: Teodor SigaevDate: 2006-12-21 18:46:25
Subject: Re: tsearch in core patch, for review
Previous:From: Teodor SigaevDate: 2006-12-21 18:29:30
Subject: Re: [HACKERS] Bundle of patches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group