Re: Review: Extensions Patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Review: Extensions Patch
Date
Msg-id AANLkTi=3KH9PfaMkQ8CohyWOvja4PSzdnLFa_gOaVPBp@mail.gmail.com
Whole thread Raw
In response to Re: Review: Extensions Patch  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Review: Extensions Patch  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Tue, Dec 7, 2010 at 4:29 PM, David E. Wheeler <david@kineticode.com> wrote:
>>> IOW, if I install extension "foo" and it does *not* have the above
>>> magic line, then this command will *not* do what I expect:
>>>
>>>    CREATE EXTENSION foo WITH SCHEMA bar;
>>>
>>> Extension "foo" will be in the public schema (usually) rather than "bar".
>>
>> Well, before that you had to explicitly write public in there, which IMO
>> is so much worse. Then again, I now think that the right way to approach
>> that is to remove this feature. The user would have a 2-steps operation
>> instead, but that works right always.
>
> Yes, that would be preferable, but a one-step operation would of course be ideal.

I think this so-called two-step approach is pretty ugly.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: serializable read only deferrable
Next
From: Fujii Masao
Date:
Subject: Re: To Signal The postmaster