Re: PgQ and pg_dump - Mailing list pgsql-general

From Michael Paquier
Subject Re: PgQ and pg_dump
Date
Msg-id CAB7nPqRMORW4yqRYZzwp-8+FhbNTCcbQH3jJKz+im-MEz+mEDA@mail.gmail.com
Whole thread Raw
In response to Re: PgQ and pg_dump  (Martín Marqués <martin@2ndquadrant.com>)
Responses Re: [HACKERS] PgQ and pg_dump  (Martín Marqués <martin@2ndquadrant.com>)
Re: PgQ and pg_dump  (Martín Marqués <martin@2ndquadrant.com>)
List pgsql-general
On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués <martin@2ndquadrant.com> wrote:
> El 16/06/16 a las 00:08, Michael Paquier escribió:
>> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués <martin@2ndquadrant.com> wrote:
>>>
>>> How would the recovery process work? We expect the schema to be there
>>> when restoring the tables?
>>
>> pg_dump creates the schema first via the CREATE EXTENSION command,
>> then tables dependent on this schema that are not created by the
>> extension are dumped individually.
>
> That's not the behavior I'm seeing here:
> [long test]

Yes, that's why I completely agree that this is a bug :)
I am seeing the same behavior as you do.

> This problem came up due to a difference between pg_dump on 9.1.12 and
> 9.1.22 (I believe it was due to a patch on pg_dump that excluded the
> dependent objects from being dumped), but here I'm using 9.5.3:

Hm. I don't recall anything in pg_dump lately except ebd092b, but that
fixed another class of problems.
--
Michael


pgsql-general by date:

Previous
From: Martín Marqués
Date:
Subject: Re: PgQ and pg_dump
Next
From: Martín Marqués
Date:
Subject: Re: [HACKERS] PgQ and pg_dump