| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, marian(dot)krucina(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13907: Restore materialized view throw permission denied |
| Date: | 2016-07-26 01:37:37 |
| Message-ID: | 9af4bc32-7e55-a21d-47e7-608582a8c48d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 7/25/16 4:09 PM, Kevin Grittner wrote:
> On Mon, Jun 27, 2016 at 1:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> I'm planning to apply the attached revision as soon as I get done
>> back-porting it.
>
> I'm thinking of applying something like the attached to fix the
> rest of this bug.
The reason that ACLs are restored last is that they could contain owner
self-revokes. So anything that you run after the ACLs could fail
because of that. I think a more complete fix would be to split up the
ACL restores into the general part, which you would run right after the
object is restored, and the owner revokes, which you would run last.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mcaustine.redondo@ph.fujitsu.com | 2016-07-26 07:27:01 | Postgresql |
| Previous Message | Michael Paquier | 2016-07-26 00:58:49 | Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse |