Re: docs: mention "pg_read_all_stats" in "track_activities" description - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: docs: mention "pg_read_all_stats" in "track_activities" description
Date
Msg-id 20220528131031.GB1876050@nathanxps13
Whole thread Raw
In response to Re: docs: mention "pg_read_all_stats" in "track_activities" description  (Michael Paquier <michael@paquier.xyz>)
Responses Re: docs: mention "pg_read_all_stats" in "track_activities" description
List pgsql-hackers
On Sat, May 28, 2022 at 05:50:35PM +0900, Michael Paquier wrote:
> On Wed, May 25, 2022 at 01:04:04PM +0900, Michael Paquier wrote:
>> Good point.  So this would give, to be exact:
>> "This information is only visible to superusers, roles with privileges
>> of the pg_read_all_stats role, and and the user owning the sessionS
>> being reported on (including sessions belonging to a role they have
>> the privileges of)."
> 
> Nathan, Ian, if you think that this could be worded better, please
> feel free to let me know.  Thanks.

Sorry, I missed this one earlier.  I'm okay with something along those
lines.  I'm still trying to think of ways to make the last part a little
clearer, but I don't have any ideas beyond what we've discussed upthread.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Roffild
Date:
Subject: Re: postgres and initdb not working inside docker
Next
From: Ranier Vilela
Date:
Subject: Re: Improving connection scalability (src/backend/storage/ipc/procarray.c)