Re: BUG #13907: Restore materialized view throw permission denied
| От | Kevin Grittner |
|---|---|
| Тема | Re: BUG #13907: Restore materialized view throw permission denied |
| Дата | |
| Msg-id | CACjxUsPu8uNHYvTtUa9v3k6nOnG+w7cc4Kr2xVagB5cUEbfBDQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #13907: Restore materialized view throw permission denied (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: BUG #13907: Restore materialized view throw permission denied
|
| Список | pgsql-bugs |
On Tue, Jul 26, 2016 at 12:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > It's possible that the most reasonable fix is to move matview refreshes to > after the ACL restoration step. That would wreak a lot of havoc with > the current view of a dump as being tripartite (pre-data/data/post-data), > so it might be more work than we want to do. But it seems like the > logically soundest thing. That is exactly what the patch I posted yesterday does. Peter was suggesting that wasn't good enough and that we should "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." I guess the idea is that we would refresh the matviews in between those two phases. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-bugs по дате отправления: