On 15 August 2012 16:30, Tom Lane wrote:
> Thom Brown writes:
>> On 12 August 2012 08:17, Thom Brown wrote:
>>> On 12 August 2012 01:06, Tom Lane wrote:
ISTM we ought to disallow that ... either the schema is inside the
extension, or vice versa, it's not sensible to say both.
>
>>> Pr
Thom Brown writes:
> On 12 August 2012 08:17, Thom Brown wrote:
>> On 12 August 2012 01:06, Tom Lane wrote:
>>> ISTM we ought to disallow that ... either the schema is inside the
>>> extension, or vice versa, it's not sensible to say both.
>> Precisely.
> Suggested changes attached. (not reall
On 12 August 2012 08:17, Thom Brown wrote:
> On 12 August 2012 01:06, Tom Lane wrote:
>> Thom Brown writes:
>>> I'm getting a dependency loop issue with pg_dump when adding a schema
>>> to an extension where the schema being added is the same as the one
>>> containing the extension.
>>
>>> CREAT
On 12 August 2012 01:06, Tom Lane wrote:
> Thom Brown writes:
>> I'm getting a dependency loop issue with pg_dump when adding a schema
>> to an extension where the schema being added is the same as the one
>> containing the extension.
>
>> CREATE EXTENSION file_fdw;
>> ALTER EXTENSION file_fdw AD
Thom Brown writes:
> I'm getting a dependency loop issue with pg_dump when adding a schema
> to an extension where the schema being added is the same as the one
> containing the extension.
> CREATE EXTENSION file_fdw;
> ALTER EXTENSION file_fdw ADD SCHEMA public;
ISTM we ought to disallow that .
Hi,
I'm getting a dependency loop issue with pg_dump when adding a schema
to an extension where the schema being added is the same as the one
containing the extension.
CREATE EXTENSION file_fdw;
ALTER EXTENSION file_fdw ADD SCHEMA public;
$ pg_dump -f /dev/null test
pg_dump: [sorter] WARNING: co
