From: Dian Fay <dian.m.fay@gmail.com>
To: pgsql-hackers@lists.postgresql.org
Subject: docs: note ownership requirement for refreshing materialized views
Date: Wed, 15 Aug 2018 19:46:49 -0400
Message-ID: <745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com> (raw)
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.
Dian Fay
Attachments:
[text/x-patch] 0001-docs-note-ownership-requirement-for-refreshing-mater.patch (572B, ../745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com/2-0001-docs-note-ownership-requirement-for-refreshing-mater.patch)
download | inline diff:diff --git a/doc/src/sgml/ref/refresh_materialized_view.sgml b/doc/src/sgml/ref/refresh_materialized_view.sgmlindex 9cf01a25a5..f001a661e1 100644--- a/doc/src/sgml/ref/refresh_materialized_view.sgml+++ b/doc/src/sgml/ref/refresh_materialized_view.sgml@@ -91,6 +91,10 @@ REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] <replaceable class="parameter">name</
<refsect1>
<title>Notes</title>
+ <para>+ Only the owner of a materialized view or a superuser can refresh it.+ </para>+
<para>
While the default index for future
<xref linkend="sql-cluster"/>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: dian.m.fay@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: docs: note ownership requirement for refreshing materialized views
In-Reply-To: <745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox