Re: BUG #13907: Restore materialized view throw permission denied
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #13907: Restore materialized view throw permission denied |
| Дата | |
| Msg-id | 17767.1469546034@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | 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 |
Kevin Grittner <kgrittn@gmail.com> writes:
> The problem we're having restoring the matview state is that not
> all ACLs needed for *SELECT* permissions are in place in time. I
> am not seeing the problem with self-revoke on REFRESH. What am I
> missing?
Uh ... that the owner might revoke his own SELECT privilege?
> One other question about the patch was what I did for testing. It
> seemed like a good idea to have dump/restore tests, but I don't see
> how to do that without leaving a role or two lingering in the
> cluster. Is that allowed?
In make installcheck, no, it is absolutely not. I'd suggest thinking
about testing this in the pg_dump TAP tests, instead, where we're just
creating a private database instance.
regards, tom lane
В списке pgsql-bugs по дате отправления: