From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, daniele(dot)varrazzo(at)gmail(dot)com |
Cc: | 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 18:24:52 |
Message-ID: | CAJ4CxLmGST-UkYzhrS-QbXLoXeYnZPPO7m7b9U=2RRr-cTArHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I'm experiencing issues with this new "feature".
My extension dynamically creates extension-owned tables and puts ACLs on
them.
When the database is dumped, it includes grants/revokes for those tables,
which will not exist when the extension is re-installed.
As a result, when the database is restored, I keep getting warnings because
it's trying to apply ACLs to tables that don't exist.
Is there a way around this issue?
On Thu, Dec 8, 2016 at 2:31 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Greetings Daniele,
>
> * daniele(dot)varrazzo(at)gmail(dot)com (daniele(dot)varrazzo(at)gmail(dot)com) wrote:
> > PostgreSQL version: 9.5.4
> [...]
> > As per title. To test:
>
> Prior to 9.6, dump/reload of an extension with custom ACLs wasn't
> really supported. This should work correctly in 9.6. Unfortunately,
> the changes required are too much to be able to back-patch to prior
> versions of PG.
>
> Thanks!
>
> Stephen
>
--
Moshe Jacobson
Principal Architect, Nead Werx Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-01-12 18:34:57 | Re: BUG #14456: pg_dump doesn't restore permissions on tables belonging to an extension |
Previous Message | Ragnar Ouchterlony | 2017-01-12 15:42:25 | Re: Problem with declarative partitioning and COPY FROM |