Re: ALTER EXTENSION UPGRADE, v3 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ALTER EXTENSION UPGRADE, v3
Date
Msg-id AANLkTikkXjtqxewTpU=19NXqpSZ4UqDhPEY23V0MxLq_@mail.gmail.com
Whole thread Raw
In response to Re: ALTER EXTENSION UPGRADE, v3  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ALTER EXTENSION UPGRADE, v3
Re: ALTER EXTENSION UPGRADE, v3
List pgsql-hackers
On Fri, Feb 11, 2011 at 12:35 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> OK, let me see if I can summarize what I think we've agreed to:
>
> CREATE syntax is extended to
>
>        CREATE EXTENSION extname [WITH] [SCHEMA s] [VERSION v] [FROM oldv]

It strikes me that if you used the same options syntax here that we're
already using for EXPLAIN and VACUUM and COPY, you wouldn't have to
worry about adding keywords for current or future options.

i.e.

CREATE EXTENSION extname [ ( option [ , ... ] ) ]

where option can be one of:

SCHEMA blah
VERSION blah
FROM blah

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Careful PL/Perl Release Not Required
Next
From: "David E. Wheeler"
Date:
Subject: Re: Careful PL/Perl Release Not Required