Robert Haas writes:
> On Fri, Feb 1, 2013 at 5:13 PM, Peter Eisentraut wrote:
>>> I wonder whether it'd not be a better idea to forbid specifying
>>> pg_catalog as the target schema for relocatable extensions.
We should do that, yes. Rationale: it's only documenting an existing
restriction that
On 02/04/2013 02:16 AM, Robert Haas wrote:
On Fri, Feb 1, 2013 at 5:13 PM, Peter Eisentraut wrote:
I wonder whether it'd not be a better idea to forbid specifying
pg_catalog as the target schema for relocatable extensions.
But that would be important, I think.
I understand the temptation to f
On Fri, Feb 1, 2013 at 5:13 PM, Peter Eisentraut wrote:
>> I wonder whether it'd not be a better idea to forbid specifying
>> pg_catalog as the target schema for relocatable extensions.
>
> But that would be important, I think.
I understand the temptation to forbid pg_catalog as the target schema
On 2/1/13 3:21 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> create extension hstore with schema pg_catalog;
>> alter extension hstore set schema public;
>> ERROR: 0A000: cannot remove dependency on schema pg_catalog because it
>> is a system object
>> drop extension hstore; -- works
>
>> I
Peter Eisentraut writes:
> create extension hstore with schema pg_catalog;
> alter extension hstore set schema public;
> ERROR: 0A000: cannot remove dependency on schema pg_catalog because it
> is a system object
> drop extension hstore; -- works
> I've seen this happen cleaning up after mistak
create extension hstore with schema pg_catalog;
alter extension hstore set schema public;
ERROR: 0A000: cannot remove dependency on schema pg_catalog because it
is a system object
drop extension hstore; -- works
I've seen this happen cleaning up after mistakenly misplaced extensions.
I suspect