| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | reach(dot)me(dot)et(at)gmail(dot)com |
| Subject: | Matview Refresh Privilege Clarification |
| Date: | 2021-02-15 13:02:44 |
| Message-ID: | 161339416452.3459.4015036841219280623@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/sql-refreshmaterializedview.html
Description:
I hope everyone is well.
I have not found it explicitly specify anywhere but from my experience I
have gathered that when you refresh a materialised view as say a Superuser
it will use the privileges of the owner of the materialized view to run the
underlying query. I am sure this bit of information would be handy to have
specified in the documentation on refreshing materialised views so as to
consider that the owner of the materialized view has the correct privileges
to the objects referenced in the query.
Stay safe,
Ettienne.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2021-02-15 15:25:09 | About the return states of SPI_execute for plpy.execute().status() |
| Previous Message | Laurenz Albe | 2021-02-15 12:53:47 | Re: Documentation on Hash and btree Indexes on jsonb |