| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: docs: mention "pg_read_all_stats" in "track_activities" description |
| Date: | 2022-06-15 17:39:25 |
| Message-ID: | 20220615173925.GB2154@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 07, 2022 at 10:08:21PM +0900, Ian Lawrence Barwick wrote:
> A little late to the party, but as an alternative suggestion for the last
> part:
>
> "... and users who either own the session being reported on, or who have
> privileges of the role to which the session belongs,"
>
> so the whole sentence would read:
>
> Note that even when enabled, this information is only visible to superusers,
> roles with privileges of the pg_read_all_stats role, and users who either own
> the session being reported on or who have privileges of the role to which the
> session belongs, so it should not represent a security risk.
This seems clearer to me.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-06-15 18:02:03 | Re: "buffer too small" or "path too long"? |
| Previous Message | Robert Haas | 2022-06-15 17:27:06 | Re: Skipping logical replication transactions on subscriber side |