Hi,
2016-06-16 9:48 GMT-03:00 Michael Paquier :
> On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués
> 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
>>> wrote:
How would the recovery process work? We expect the schema to
On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués 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
>> wrote:
>>>
>>> How would the recovery process work? We expect the schema to be there
>>> when restoring the tables?
>>
>> pg_dump crea
El 16/06/16 a las 00:08, Michael Paquier escribió:
> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués
> 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 ta
On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués wrote:
> Hi Michael,
>
> 2016-06-15 5:00 GMT-03:00 Michael Paquier :
>> Martin wrote:
>>> I wonder if this is the desirable way of handling pgq, or if those
>>> tables should be dumped. I'm starting to think that this is a PgQ bug,
>>> or maybe it's
Hi Michael,
2016-06-15 5:00 GMT-03:00 Michael Paquier :
> Martin wrote:
>> I wonder if this is the desirable way of handling pgq, or if those
>> tables should be dumped. I'm starting to think that this is a PgQ bug,
>> or maybe it's not a good idea to install PgQ as an extension.
>
> As I am looki
Martin wrote:
> I wonder if this is the desirable way of handling pgq, or if those
> tables should be dumped. I'm starting to think that this is a PgQ bug,
> or maybe it's not a good idea to install PgQ as an extension.
As I am looking at that I would qualify that as a bug in pg_dump.
Schemas can