| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Moshe Jacobson <moshe(at)neadwerx(dot)com>, 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 19:16:32 |
| Message-ID: | 13549.1484248592@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> Hmm. There's an argument to be made that ALTER EXTENSION ADD should
>> absorb whatever the object's current ACLs are into the pg_init_privs
>> entries for the extension. (I don't think it does that now, though
>> I might be wrong.) However ...
> I've not gone and looked yet, but I doubt that it does. I think I can
> agree with the argument that it really should add those ACLs to
> pg_init_privs. Of course, any furhter manipulation of the ACLs from
> that point will cause those ACLs to be included in the pg_dump.
> I'll take a look at ALTER EXTENSION ADD and pg_init_privs.
By the same token, does ALTER EXTENSION DROP remove those entries?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-01-12 19:24:38 | Re: BUG #14456: pg_dump doesn't restore permissions on tables belonging to an extension |
| Previous Message | Moshe Jacobson | 2017-01-12 19:10:29 | Re: BUG #14456: pg_dump doesn't restore permissions on tables belonging to an extension |