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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: docs: mention "pg_read_all_stats" in "track_activities" description
Date: 2022-05-20 23:08:37
Message-ID: 20220520230837.GB877934@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, May 20, 2022 at 03:17:29PM +0900, Ian Lawrence Barwick wrote:
> It seems reasonable to mention here that the information is also visible to
> members of "pg_read_all_stats", similar to what is done in the
> pg_stat_statements
> docs [2].
> [2]
> Suggested wording:
>> Note that even when enabled, this information is only visible to superusers,
>> members of the <literal>pg_read_all_stats</literal> role and the user owning
>> the session being reported on, so it should not represent a security risk.
> Patch (for HEAD) with suggested wording attached; the change should
> IMO be applied
> all the way back to v10 (though as-is the patch only applies to HEAD,
> can provide
> others if needed).


Nathan Bossart
Amazon Web Services:

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2022-05-20 23:08:49 Re: Limiting memory allocation
Previous Message Nathan Bossart 2022-05-20 23:04:29 Re: PG15 beta1 fix pg_stat_statements view document