Re: proposal: hide application_name from other users

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Harold Giménez <harold(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: hide application_name from other users
Date: 2014-01-21 16:10:10
Message-ID: CABUevEwxM0+uH38yd2sf5onk+7OFAUEjN9k72CBPYjzb+3=f-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 21, 2014 at 2:41 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>wrote:

> Stephen Frost wrote:
> > * Craig Ringer (craig(at)2ndquadrant(dot)com) wrote:
> > > It also means that monitoring tools must run as superuser to see
> > > information they require, which to me is a total showstopper.
> >
> > We've already got *far* too much of that going on for my taste. I'd
> > love to see a comprehensive solution to this problem which allows
> > monitoring systems to run w/o superuser privileges.
>
> Yeah, we need a CAP_MONITOR capability thingy. (CAP_BACKUP would be
> great too -- essentially "read only but read everything")
>

Isn't CAP_BACKUP pretty much the REPLICATION privilege?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-01-21 16:15:18 Re: currawong is not a happy animal
Previous Message Simon Riggs 2014-01-21 16:06:08 Re: Hard limit on WAL space used (because PANIC sucks)