| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] PgQ and pg_dump |
| Date: | 2016-06-21 16:08:28 |
| Message-ID: | CA+TgmoZ715iH7z5exBPxArxk2enip7MpDmK+QAajj8fpymv+xw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, Jun 16, 2016 at 1:46 PM, Martín Marqués <martin(at)2ndquadrant(dot)com> wrote:
> The comment is accurate on what is going to be dumpable and what's not
> from the code. In our case, as the pgq schema is not dumpable becaause
> it comes from an extension, other objects it contain will not be
> dumpable as well.
>
> That's the reason why the PgQ event tables created by
> pgq.create_queue() are not dumped.
That sucks.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Marqués | 2016-06-21 16:45:19 | Re: [HACKERS] PgQ and pg_dump |
| Previous Message | Job | 2016-06-21 15:59:18 | R: R: Vacuum full: alternatives? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-06-21 16:12:34 | Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0 |
| Previous Message | Robert Haas | 2016-06-21 16:03:23 | Re: Hash Indexes |