Re: PgQ and pg_dump
От | Michael Paquier |
---|---|
Тема | Re: PgQ and pg_dump |
Дата | |
Msg-id | CAB7nPqRjoQfUWcF3L_pm+wHYLpkbmkc+pLoca6XXS3X28BeTBw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PgQ and pg_dump (Martín Marqués <martin@2ndquadrant.com>) |
Ответы |
Re: PgQ and pg_dump
|
Список | pgsql-general |
On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués <martin@2ndquadrant.com> wrote: > Hi Michael, > > 2016-06-15 5:00 GMT-03:00 Michael Paquier <michael.paquier@gmail.com>: >> 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 be part of the extension definition and be linked to it, >> and tables created on top of the schema defined in the extension >> should really be dumped.. > > 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. -- Michael
В списке pgsql-general по дате отправления: