Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
| От | Bruce Momjian |
|---|---|
| Тема | Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view |
| Дата | |
| Msg-id | Ze-SDjLjiBfSvGlE@momjian.us обсуждение |
| Ответ на | Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view (Heikki Linnakangas <hlinnaka@iki.fi>) |
| Список | pgsql-bugs |
On Tue, Mar 12, 2024 at 01:02:16AM +0200, Heikki Linnakangas wrote: > On 11/03/2024 22:10, PG Bug reporting form wrote: > > Reproducer log (starting from interesting part): > > test=# REFRESH MATERIALIZED VIEW CONCURRENTLY test_mv; > > REFRESH MATERIALIZED VIEW > > test=# alter materialized view test_mv owner to test_role; > > ALTER MATERIALIZED VIEW > > test=# REFRESH MATERIALIZED VIEW CONCURRENTLY test_mv; > > ERROR: permission denied for table test > > --what??? N1 > > > > --check that im not hallucinating > > test=# select * from test; > > val > > ----- > > 1 > > (1 row) > > So far, this is working correctly. REFRESH MATERIALIZED VIEW runs with the > permissions of the materialized view's owner. In this case, the owner is > 'test_role', which doesn't have select permission on the table. Can we do a better job of suggesting the cause of the failure? -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.
В списке pgsql-bugs по дате отправления: