Re: Interface for pg_autovacuum - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Interface for pg_autovacuum
Date
Msg-id 87psad156u.fsf@enterprisedb.com
Whole thread Raw
In response to Re: Interface for pg_autovacuum  ("Jim Nasby" <jim.nasby@enterprisedb.com>)
Responses Re: Interface for pg_autovacuum
List pgsql-hackers
"Jim Nasby" <jim.nasby@enterprisedb.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"...

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.


--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "Jim Nasby"
Date:
Subject: Re: Interface for pg_autovacuum
Next
From: Andrew Dunstan
Date:
Subject: Re: Interface for pg_autovacuum