Re: docs: note ownership requirement for refreshing materialized views
Jonathan Katz <jonathan.katz@excoventures.com>
From: "Jonathan S. Katz" <jonathan.katz@excoventures.com>
To: Dian Fay <dian.m.fay@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2018-08-16T01:06:34Z
Lists: pgsql-hackers
Attachments
- 0001-treat-refresh-mat-view-as-mat-view.patch (application/octet-stream) patch 0001
Hi Dian, > On Aug 15, 2018, at 7:46 PM, Dian Fay <dian.m.fay@gmail.com> wrote: > > hi all! I discovered today that the REFRESH MATERIALIZED VIEW documentation doesn't mention that only the owner (or a superuser) may actually perform the refresh operation. This patch adds a note to that effect. I played around with this feature a bit and did see this was the case. Also while playing around I noticed the error message was as such: test=> REFRESH MATERIALIZED VIEW blah; ERROR: must be owner of relation blah But it’s not a relation, it’s a materialized view. I attached a patch that I think should fix this. Kudos to Dave Cramer who was sitting next to me helping me to locate files and confirm assumptions. Jonathan
Commits
-
Mention ownership requirements for REFRESH MATERIALIZED VIEW in docs
- b6c994af1f0d 9.3.25 landed
- 777192f0dd44 9.4.20 landed
- 82784f088986 9.5.15 landed
- 86e873c01650 9.6.11 landed
- 0dfaf8f763ae 10.6 landed
- b43cf1dcded9 11.0 landed
- ee8012481190 12.0 landed