From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: restrict pg_stat_ssl to superuser?
Date: Tue, 19 Feb 2019 16:57:52 +0100
Message-ID: <1d1bf3a7-955e-ce6b-de99-b900136ca789@2ndquadrant.com> (raw)
In-Reply-To: <20190218035813.GH15532@paquier.xyz>
References: <63117976-d02c-c8e2-3aef-caa31a5ab8d3@2ndquadrant.com>
<20190212064007.GN1475@paquier.xyz>
<71319f2d-a073-0499-4562-6003e026307e@2ndquadrant.com>
<20190218035813.GH15532@paquier.xyz>
On 2019-02-18 04:58, Michael Paquier wrote:
> On Fri, Feb 15, 2019 at 02:04:59PM +0100, Peter Eisentraut wrote:
>> We could remove default privileges from pg_stat_get_activity(). Would
>> that be a problem?
>
> I don't think so, still I am wondering about the impact that this
> could have for monitoring tools calling it directly as we document
> it..
Actually, this approach isn't going to work anyway, because function
permissions in a view are checked as the current user, not the view owner.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, michael@paquier.xyz
Subject: Re: restrict pg_stat_ssl to superuser?
In-Reply-To: <1d1bf3a7-955e-ce6b-de99-b900136ca789@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox