Permission to refresh materialized view
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.
Is that intended behaviour? Is there a way to enable the user to refresh
materialized views in that schema?
Regards
Johann
--
Because experiencing your loyal love is better than life itself,
my lips will praise you. (Psalm 63:3)
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.klaver@aklaver.com
-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@aklaver.com]
Sent: Wednesday, March 13, 2019 10:24 AM
To: Johann Spies <johann.spies@gmail.com>; pgsql-general@postgresql.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.klaver@aklaver.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
On 3/17/19 11:52 PM, Johann Spies wrote:
Please reply to list also.
Ccing list.
On Wed, 13 Mar 2019 at 16:24, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:On 3/13/19 6:27 AM, Johann Spies wrote:
...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?
[42501] ERROR: must be owner of materialized view xxx_mv
Regards
Johann
--
Because experiencing your loyal love is better than life itself,
my lips will praise you. (Psalm 63:3)
--
Adrian Klaver
adrian.klaver@aklaver.com
Import Notes
Reply to msg id not found: CAGZ55DQyg6fw=O6AAUL4050mTRH1rj_NLfiX4WLwXXNtog0GgA@mail.gmail.com
From documentation:
"REFRESH MATERIALIZED VIEW completely replaces the contents of a materialized view. To execute this command you must be the owner of the materialized view."
So it is intended behavior.
https://www.postgresql.org/docs/11/sql-refreshmaterializedview.html
________________________________________
Från: Adrian Klaver [adrian.klaver@aklaver.com]
Skickat: den 18 mars 2019 15:51
Till: Johann Spies
Kopia: pgsql-general
Ämne: Re: Permission to refresh materialized view
On 3/17/19 11:52 PM, Johann Spies wrote:
Please reply to list also.
Ccing list.
On Wed, 13 Mar 2019 at 16:24, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:On 3/13/19 6:27 AM, Johann Spies wrote:
...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?
[42501] ERROR: must be owner of materialized view xxx_mv
Regards
Johann
--
Because experiencing your loyal love is better than life itself,
my lips will praise you. (Psalm 63:3)
--
Adrian Klaver
adrian.klaver@aklaver.com