Re: proposal: hide application_name from other users
От | Josh Berkus |
---|---|
Тема | Re: proposal: hide application_name from other users |
Дата | |
Msg-id | 52DF166E.6060207@agliodbs.com обсуждение исходный текст |
Ответ на | proposal: hide application_name from other users (Harold Giménez <harold@heroku.com>) |
Ответы |
Re: proposal: hide application_name from other users
Re: proposal: hide application_name from other users |
Список | 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
В списке pgsql-hackers по дате отправления: