Re: BUG #14456: pg_dump doesn't restore permissions on tables belonging to an extension

Moshe Jacobson <moshe(at)neadwerx(dot)com> writes:
> On Thu, Jan 12, 2017 at 2:01 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I think this scenario is simply pilot error, or at least gross abuse of
>> the extension system. If you dump and reload a DB containing an extension,
>> the extension definition that's fetched by CREATE EXTENSION is expected
>> to define (at least) all the objects that belonged to the extension in the
>> old DB. You can't just randomly ALTER EXTENSION and not update the
>> extension definition script to match.

> The reason I add the dynamically-created tables to the extension is so that
> they are never included in the pg_dump output. If this is a gross abuse of
> the extension system, is there another way you can suggest to mark these
> tables as not-to-be-dumped?

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?

regards, tom lane