From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | avi Singh <avisingh19811981(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [GENERAL] grant select on pg_stat_activity |
Date: | 2016-03-18 21:46:46 |
Message-ID: | 56EC7746.80406@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On 03/18/2016 01:09 PM, avi Singh wrote:
> Guys
> Whats the best way to grant select on pg_stat_activity so that
> non super user can access this view.
They should be able to, see below. If that is not your case, then more
information is needed.
guest(at)test=> select current_user;
current_user
--------------
guest
(1 row)
guest(at)test=> \du guest
List of roles
Role name | Attributes | Member of
-----------+------------+-----------
guest | | {}
guest(at)test=> select * from pg_stat_activity;
-[ RECORD 1 ]----+--------------------------------
datid | 16385
datname | test
pid | 2622
usesysid | 1289138
usename | guest
application_name | psql
client_addr |
client_hostname |
client_port | -1
backend_start | 2016-03-18 14:41:43.906754-07
xact_start | 2016-03-18 14:44:22.550742-07
query_start | 2016-03-18 14:44:22.550742-07
state_change | 2016-03-18 14:44:22.550746-07
waiting | f
state | active
backend_xid |
backend_xmin | 58635
query | select * from pg_stat_activity;
>
> Thanks
> Avi
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-03-19 14:09:47 | Re: Error: insufficient data in the message |
Previous Message | Peter Geoghegan | 2016-03-18 21:29:51 | Re: ON CONFLICT DO NOTHING RETURNING |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2016-03-19 02:44:55 | Re: Searching GIN-index (FTS) and sort by timestamp-column |
Previous Message | avi Singh | 2016-03-18 20:09:56 | grant select on pg_stat_activity |