postgres.git / summary / log / commit / refs

commit    0f53934164d37682fd6a6d87d57008f9ca03e3d0
Author:   Peter Eisentraut <peter_e@gmx.net>
Date:     Thu Nov 02 16:12:23 2017 +0000
First released in: 11.0

    doc: Clarify pgstattuple privileges information
    
    The description has gotten a bit confusing over time, so rewrite the
    paragraph a bit.
    
    Reported-by: Feike Steenbergen <feikesteenbergen@gmail.com>


 doc/src/sgml/pgstattuple.sgml | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/doc/src/sgml/pgstattuple.sgml b/doc/src/sgml/pgstattuple.sgml
index 611df9d0bfd..04a4423dc54 100644
--- a/doc/src/sgml/pgstattuple.sgml
+++ b/doc/src/sgml/pgstattuple.sgml
@@ -13,12 +13,14 @@
  </para>
 
  <para>
-  As these functions return detailed page-level information, only the superuser
-  has EXECUTE privileges on them upon installation.  After the functions have
-  been installed, users may issue <command>GRANT</command> commands to change
-  the privileges on the functions to allow non-superusers to execute them. Members
-  of the <literal>pg_stat_scan_tables</literal> role are granted access by default. See
-  the description of the <xref linkend="sql-grant"> command for specifics.
+  Because these functions return detailed page-level information, access is
+  restricted by default.  By default, only the
+  role <literal>pg_stat_scan_tables</literal> has <literal>EXECUTE</literal>
+  privilege.  Superusers of course bypass this restriction.  After the
+  extension has been installed, users may issue <command>GRANT</command>
+  commands to change the privileges on the functions to allow others to
+  execute them.  However, it might be preferable to add those users to
+  the <literal>pg_stat_scan_tables</literal> role instead.
  </para>
 
  <sect2>


[parent: 7b6c07547190]