From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: restrict pg_stat_ssl to superuser?
Date: Thu, 7 Feb 2019 09:30:38 +0100
Message-ID: <63117976-d02c-c8e2-3aef-caa31a5ab8d3@2ndquadrant.com> (raw)
As discussed in [0], should we restrict access to pg_stat_ssl to
superusers (and an appropriate pg_ role)?
If so, is there anything in that view that should be made available to
non-superusers? If not, then we could perhaps do this via a simple
permission change instead of going the route of blanking out individual
columns.
[0]:
<https://www.postgresql.org/message-id/flat/398754d8-6bb5-c5cf-e7b8-22e5f0983caf@2ndquadrant.com;
--
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
Subject: Re: restrict pg_stat_ssl to superuser?
In-Reply-To: <63117976-d02c-c8e2-3aef-caa31a5ab8d3@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