From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: restrict pg_stat_ssl to superuser? |
Date: | 2019-02-21 08:11:24 |
Message-ID: | 20190221081124.GS15532@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 20, 2019 at 11:51:08AM +0100, Peter Eisentraut wrote:
> So here is a patch doing it the "normal" way of nulling out all the rows
> the user shouldn't see.
That looks fine to me.
> I haven't found any documentation of these access restrictions in the
> context of pg_stat_activity. Is there something that I'm not seeing or
> something that should be added?
Yes, there is nothing. I agree that it would be good to mention that
some fields are set to NULL and only visible to superusers or members of
pg_read_all_stats with a note for pg_stat_activity and
pg_stat_get_activity(). Here is an idea:
"Backend and SSL information are restricted to superusers and members
of the <literal>pg_read_all_stats</literal> role. Access may be
granted to others using <command>GRANT</command>.
Getting that back-patched would be nice where pg_read_all_stats was
introduced.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Jamison, Kirk | 2019-02-21 08:20:55 | RE: Timeout parameters |
Previous Message | Iwata, Aya | 2019-02-21 08:11:11 | RE: libpq debug log |