Re: proposal: hide application_name from other users

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Harold Giménez <harold(at)heroku(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: proposal: hide application_name from other users
Date: 2014-01-22 00:01:31
Message-ID: 20140122000131.GG29396@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 21, 2014 at 03:57:37PM -0800, Harold Giménez wrote:
> > It also means that monitoring tools must run as superuser to see
> > information they require, which to me is a total showstopper.
>
>
> Well, the fact is that if you don't run monitoring tools as superuser,
> there may not be enough connection slots available anyways, in cases
> where actual usage is consuming all of max_connections, and only the
> reserved slots are available. So in a way it's already unreliable to
> run monitoring as non-superuser unfortunately.

You might need to run as superuser in these cases, but it is hard to see
why would need to do that in the normal case.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-01-22 00:02:39 Re: ALTER SYSTEM SET typos and fix for temporary file name management
Previous Message Tom Lane 2014-01-21 23:59:13 Re: Hard limit on WAL space used (because PANIC sucks)