Re: SuperUser check in pg_stat_statements - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: SuperUser check in pg_stat_statements
Date
Msg-id 56256AB8.10501@BlueTreble.com
Whole thread Raw
In response to Re: SuperUser check in pg_stat_statements  (rajan <vgmonnet@gmail.com>)
Responses Re: SuperUser check in pg_stat_statements  (Lukas Fittl <lukas@fittl.com>)
Re: SuperUser check in pg_stat_statements  (rajan <vgmonnet@gmail.com>)
List pgsql-hackers
On 10/19/15 3:48 PM, rajan wrote:
> Thanks Stephen and Shulgin for your response.
>
> Will go through the patch and will try to solve my problem using that.
>
> My scenario is that i need to have an user who cannot be a super user but a
> monitor user, who will be able to see all the queries executed by all users.

You can set that up today by defining a view on top of 
pg_stat_statements (or maybe it needs a SECDEF SRF... been a while since 
I've done it).
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Foreign join pushdown vs EvalPlanQual
Next
From: Jim Nasby
Date:
Subject: Re: Why no CONSTANT for row variables in plpgsql?