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

From Lukas Fittl
Subject Re: SuperUser check in pg_stat_statements
Date
Msg-id CAP53Pkw-7oZBrhBBB7_U=ijQcuReSxzwW27j44yX7t9gKPC64Q@mail.gmail.com
Whole thread Raw
In response to Re: SuperUser check in pg_stat_statements  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: SuperUser check in pg_stat_statements
List pgsql-hackers
On Mon, Oct 19, 2015 at 3:12 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
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).

You can solve this using a security definer method created by a superuser, see


for a full example.

--
Lukas Fittl

Skype: lfittl
Phone: +1 415 321 0630

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Why no CONSTANT for row variables in plpgsql?
Next
From: Jim Nasby
Date:
Subject: Re: Why no CONSTANT for row variables in plpgsql?