Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 0f53934

Browse files
committed
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>
1 parent 7b6c075 commit 0f53934

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

doc/src/sgml/pgstattuple.sgml

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,14 @@
1313
</para>
1414

1515
<para>
16-
As these functions return detailed page-level information, only the superuser
17-
has EXECUTE privileges on them upon installation. After the functions have
18-
been installed, users may issue <command>GRANT</command> commands to change
19-
the privileges on the functions to allow non-superusers to execute them. Members
20-
of the <literal>pg_stat_scan_tables</literal> role are granted access by default. See
21-
the description of the <xref linkend="sql-grant"> command for specifics.
16+
Because these functions return detailed page-level information, access is
17+
restricted by default. By default, only the
18+
role <literal>pg_stat_scan_tables</literal> has <literal>EXECUTE</literal>
19+
privilege. Superusers of course bypass this restriction. After the
20+
extension has been installed, users may issue <command>GRANT</command>
21+
commands to change the privileges on the functions to allow others to
22+
execute them. However, it might be preferable to add those users to
23+
the <literal>pg_stat_scan_tables</literal> role instead.
2224
</para>
2325

2426
<sect2>

0 commit comments

Comments
 (0)