| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Henrik Uggla <Henrik(dot)Uggla(at)kristianstad(dot)se> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Refreshing materialized views |
| Date: | 2017-11-28 14:25:47 |
| Message-ID: | 13279.1511879147@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Henrik Uggla <Henrik(dot)Uggla(at)kristianstad(dot)se> writes:
> I created some materialized views and set a group as owner. My problem is that I can't refresh the views. I get "permission denied" even when using the postgres super user. If I change the owner to an ordinary user I still can't refresh the view as the owner or postgres. Only if I change owner to postgres am I able to refresh the view, but only as the postgres user. I've mainly tried with Pgadmin4 but also a few times with psql, and the database is installed as a docker container. Please help.
Apparently, the view owner lacks select permission on some underlying
table. Pay attention to what is being denied access to.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-11-28 14:35:33 | Re: Plan for update ... where a is not distinct from b |
| Previous Message | Tom Lane | 2017-11-28 14:22:48 | Re: vacuumdb fails with error pg_statistic_relid_att_inh_index constraint violation after upgrade to 9.6 |