pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dian Fay <dian.m.fay@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: docs: note ownership requirement for refreshing materialized views
Date: Thu, 16 Aug 2018 00:07:30 -0400
Message-ID: <13833.1534392450@sss.pgh.pa.us> (raw)
In-Reply-To: <a1ccf5bd-f69c-6b73-77a0-6b6e719e01de@gmail.com>
References: <745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com>
	<20180816010355.GH3681@paquier.xyz>
	<a1ccf5bd-f69c-6b73-77a0-6b6e719e01de@gmail.com>

Dian Fay <dian.m.fay@gmail.com> writes:
> 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!

I think Michael's point is that this formulation is unlike what we have
elsewhere for similar statements.  Looking around, it seems like the
typical phraseology would be more like

"You must own the materialized view to use REFRESH MATERIALIZED VIEW."

It is not really customary to call out the superuser exception
explicitly, because if we did, we'd be mentioning superusers in every
other sentence.  The point is covered by existing documentation that
says something to the effect of superusers bypassing all permissions
checks; and I think there's also a statement somewhere about superusers
implicitly being members of every role, which is a different way of
arriving at the same conclusion.

In any case, it's definitely an oversight that the REFRESH reference
page fails to address permissions at all.  +1 for adding something.

			regards, tom lane




view thread (15+ messages)  latest in thread

Message-ID: <13833.1534392450@sss.pgh.pa.us>
Permalink:  ../13833.1534392450@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13833.1534392450@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, 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: <13833.1534392450@sss.pgh.pa.us>

* 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