Re: proposal: hide application_name from other users - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: proposal: hide application_name from other users
Date
Msg-id 52E80B78.5070505@agliodbs.com
Whole thread Raw
In response to proposal: hide application_name from other users  (Harold Giménez <harold@heroku.com>)
Responses Re: proposal: hide application_name from other users  (Greg Stark <stark@mit.edu>)
Re: proposal: hide application_name from other users  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: proposal: hide application_name from other users  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 01/28/2014 07:27 AM, Greg Stark wrote:
> Why is application_name useful for users who aren't the DBA and aren't
> the user in question. The sql_query would probably be more useful than
> application_name but we hide that...

I have non-privileged monitoring scripts do counts of connections by
application name all the time as a way of checking for runaway
applications, and would be quite put out by restricting this to superusers.

Really the only way we're going to solve this is to make column
permissions on special system views fully configurable.

For example, I would really like to GRANT an unpriv user access to the
WAL columns in pg_stat_replication so that I can monitor replication
delay without granting superuser permissions.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: proposal: hide application_name from other users
Next
From: Noah Misch
Date:
Subject: Re: UNION ALL on partitioned tables won't use indices.