Re: Review: Extensions Patch

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Review: Extensions Patch
Date: 2010-12-08 03:44:47
Message-ID: AANLkTi=3KH9PfaMkQ8CohyWOvja4PSzdnLFa_gOaVPBp@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 7, 2010 at 4:29 PM, David E. Wheeler <david(at)kineticode(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-12-08 03:47:43 Re: To Signal The postmaster
Previous Message Tom Lane 2010-12-08 01:36:13 Re: serializable read only deferrable