| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Harold Giménez <harold(at)heroku(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: proposal: hide application_name from other users |
| Date: | 2014-01-22 00:53:02 |
| Message-ID: | 52DF166E.6060207@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/21/2014 04:12 AM, Stephen Frost 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.
>
Agreed. I just ran into the issue that getting data out of
pg_stat_replication on replication lag requires superuser privs, which
is annoying; without that, I can run Handyrep entirely as an
unprivileged user, but that one fact requires the handyrep database user
to be a superuser.
It would be really nice to be able to GRANT/REVOKE on some of these
special system views ...
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Harold Giménez | 2014-01-22 00:57:16 | Re: proposal: hide application_name from other users |
| Previous Message | Harold Giménez | 2014-01-22 00:52:56 | Re: proposal: hide application_name from other users |