Re: SuperUser check in pg_stat_statements
От | Lukas Fittl |
---|---|
Тема | Re: SuperUser check in pg_stat_statements |
Дата | |
Msg-id | CAP53Pkw-7oZBrhBBB7_U=ijQcuReSxzwW27j44yX7t9gKPC64Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: SuperUser check in pg_stat_statements (Jim Nasby <Jim.Nasby@BlueTreble.com>) |
Ответы |
Re: SuperUser check in pg_stat_statements
|
Список | pgsql-hackers |
On Mon, Oct 19, 2015 at 3:12 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
You can solve this using a security definer method created by a superuser, see
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).
for a full example.
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
Skype: lfittl
Phone: +1 415 321 0630
В списке pgsql-hackers по дате отправления: