Re: BUG #13907: Restore materialized view throw permission denied
От | Peter Eisentraut |
---|---|
Тема | Re: BUG #13907: Restore materialized view throw permission denied |
Дата | |
Msg-id | 9af4bc32-7e55-a21d-47e7-608582a8c48d@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: BUG #13907: Restore materialized view throw permission denied (Kevin Grittner <kgrittn@gmail.com>) |
Ответы |
Re: BUG #13907: Restore materialized view throw permission denied
|
Список | pgsql-bugs |
On 7/25/16 4:09 PM, Kevin Grittner wrote: > On Mon, Jun 27, 2016 at 1:35 PM, Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-bugs по дате отправления: