| From: | Feike Steenbergen <feikesteenbergen(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Document pgstattuple privileges without ambiguity |
| Date: | 2017-08-21 07:47:45 |
| Message-ID: | CAK_s-G1PETi-in3fAN-wTXYe_JMBstwG9__+wBAXxmyyWDQZ6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
When installing pgstattuple on 10, the documentation about its
privileges was unclear to me. (Does the pg_stat_scan_tables role get
EXECUTE privileges by default or not?).
By making the privilege paragraph less verbose and a duplicate of the
paragraph used for pgfreespacemap and pgbuffercache we remove the
ambiguity and make the documentation more uniform.
The replacement paragrahp is much less verbose and loses some detailed
pointers (to GRANT syntax), but in this instance I feel less is more.
Regards,
Feike
| Attachment | Content-Type | Size |
|---|---|---|
| pgstattuple_privilege_documentation_v1.patch | application/octet-stream | 913 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2017-08-21 07:59:48 | Re: assorted code cleanup |
| Previous Message | Chris Travers | 2017-08-21 07:42:38 | Re: [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database? |