From: | "Day, David" <david(dot)day(at)redcom(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Johann Spies <johann(dot)spies(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: Permission to refresh materialized view |
Date: | 2019-03-13 14:47:41 |
Message-ID: | 87d631cf993c4cd6aa1f6e28d82717b1@exch-02.redcom.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)aklaver(dot)com]
Sent: Wednesday, March 13, 2019 10:24 AM
To: Johann Spies <johann(dot)spies(at)gmail(dot)com>; pgsql-general(at)postgresql(dot)org
Subject: Re: Permission to refresh materialized view
On 3/13/19 6:27 AM, Johann Spies wrote:
> We did run this query:
>
> /GRANT ALL ON ALL TABLES IN SCHEMA X TO USER Y;/ / / But user Y gets
> the message that he has to be the owner of a materialized view to be
> able to refresh it.
What is the exact message?
>
> Is that intended behaviour? Is there a way to enable the user to
> refresh materialized views in that schema?
What is the definition of the view?
>
> Regards
> Johann
> //
>
> --
> Because experiencing your loyal love is better than life itself, my
> lips will praise you. (Psalm 63:3)
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
--
Lacking the actual error message however:
Y might lack usage on the containing schema ?
Y might lack privilege on a function or sequence contained in the view ?
Dave Day
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2019-03-13 15:38:16 | Re: Where to store Blobs? |
Previous Message | Laurenz Albe | 2019-03-13 14:33:50 | Re: Where to store Blobs? |