Re: SuperUser check in pg_stat_statements

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: rajan <vgmonnet(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SuperUser check in pg_stat_statements
Date: 2015-10-19 22:12:08
Message-ID: 56256AB8.10501@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-10-19 22:16:22 Re: Why no CONSTANT for row variables in plpgsql?
Previous Message Robert Haas 2015-10-19 22:07:50 Re: Foreign join pushdown vs EvalPlanQual