From: Dian Fay <dian.m.fay@gmail.com>
Subject: docs: note ownership requirement for refreshing materialized views
To: pgsql-hackers@lists.postgresql.org
Message-ID: <745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com>
Date: Wed, 15 Aug 2018 19:46:49 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="------------AFED250155A498D92E227814"
Content-Language: en-HK
Precedence: bulk

This is a multi-part message in MIME format.
--------------AFED250155A498D92E227814
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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


--------------AFED250155A498D92E227814
Content-Type: text/x-patch;
 name="0001-docs-note-ownership-requirement-for-refreshing-mater.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename*0="0001-docs-note-ownership-requirement-for-refreshing-mater.pa";
 filename*1="tch"

diff --git a/doc/src/sgml/ref/refresh_materialized_view.sgml b/doc/src/sgml/ref/refresh_materialized_view.sgml
index 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"/>

--------------AFED250155A498D92E227814--