| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Moshe Jacobson <moshe(at)neadwerx(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, daniele(dot)varrazzo(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14456: pg_dump doesn't restore permissions on tables belonging to an extension |
| Date: | 2017-01-12 21:27:56 |
| Message-ID: | 19310.1484256476@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> Moshe Jacobson <moshe(at)neadwerx(dot)com> writes:
>>> The reason I add the dynamically-created tables to the extension is so that
>>> they are never included in the pg_dump output.
>> The extension mechanism definitely isn't meant to do that ;-). Maybe
>> you could put these not-to-dump tables in their own schema and exclude
>> that schema from pg_dump with -N?
> Is this related to this commit?
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=f2fcad27d59c8e5c48f8fa0a96c8355e40f24273
Seems like it doesn't quite match Moshe's use case --- he *doesn't* want
those tables dumped. I'm not sure if he cares whether they have
dependencies on the extension.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathon Nelson | 2017-01-13 14:47:06 | Re: Bug in Physical Replication Slots (at least 9.5)? |
| Previous Message | Alvaro Herrera | 2017-01-12 21:22:08 | Re: BUG #14456: pg_dump doesn't restore permissions on tables belonging to an extension |