From: Dian Fay <dian.m.fay@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: docs: note ownership requirement for refreshing materialized views
Date: Wed, 15 Aug 2018 21:44:46 -0400
Message-ID: <a1ccf5bd-f69c-6b73-77a0-6b6e719e01de@gmail.com> (raw)
In-Reply-To: <20180816010355.GH3681@paquier.xyz>
References: <745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com>
<20180816010355.GH3681@paquier.xyz>
I feel resorting to the infinitive asks more involvement of the reader,
while leading with the responsible role(s) helps shortcut the process of
determining whether what follows is relevant. Efficiency is always a
virtue, although this is admittedly more than a little academic for a
one-sentence addition!
On 8/15/18 9:03 PM, Michael Paquier wrote:
> On Wed, Aug 15, 2018 at 07:46:49PM -0400, Dian Fay 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 think that's a good idea. I would rewrite that a bit differently, like:
> To refresh a materialized view, one must be the materalized view's owner
> or a superuser.
>
> Thougts or objections?
> --
> Michael
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, michael@paquier.xyz, pgsql-hackers@lists.postgresql.org
Subject: Re: docs: note ownership requirement for refreshing materialized views
In-Reply-To: <a1ccf5bd-f69c-6b73-77a0-6b6e719e01de@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