| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tim Clarke <tim(dot)clarke(at)minerva(dot)info> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: accessing cross-schema materialized views |
| Date: | 2021-03-31 22:42:05 |
| Message-ID: | 3337912.1617230525@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tim Clarke <tim(dot)clarke(at)minerva(dot)info> writes:
> We have:
> create materialized view schema1.matview.....
> grant select on table schema1.matview to mygroup
> create view schema2.usingview as select ... from schema1.matview
> grant select on table schema2.using to mygroup
> and yet we receive "permission denied for materialized view" on a user with the mygroup role selecting from schema2.usingview?
The owner of the schema2.usingview is the one who must have
privilege to read the underlying schema1.matview. Our
permissions messages are, I fear, frequently not very good
about saying whose privileges were checked.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glen Huang | 2021-04-01 01:51:38 | How to implement expiration in PostgreSQL? |
| Previous Message | Rob Sargent | 2021-03-31 22:36:50 | Re: accessing cross-schema materialized views |