Re: docs: mention "pg_read_all_stats" in "track_activities" description

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Ian Lawrence Barwick <barwick(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: docs: mention "pg_read_all_stats" in "track_activities" description
Date: 2022-05-28 13:10:31
Message-ID: 20220528131031.GB1876050@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2022-05-28 14:12:47 Re: Improving connection scalability (src/backend/storage/ipc/procarray.c)
Previous Message Roffild 2022-05-28 12:59:40 Re: postgres and initdb not working inside docker