Re: log_statement GUC parameter - Mailing list pgsql-general

From Mladen Gogala
Subject Re: log_statement GUC parameter
Date
Msg-id 4534f313-b374-2dc4-d0a4-5d301981a089@gmail.com
Whole thread Raw
In response to Re: log_statement GUC parameter  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thank you Tom! It turns out that the Oracle way of doing things 
(SECURITY DEFINER) was the wrong way here. Thanks a bunch.

On 8/12/21 4:37 PM, Tom Lane wrote:
> ctually, for that specific requirement, there's an easier way:
>
>     ALTER USER target_user SET log_statement = 'all';
>
> While the target_user can't do that for himself, a superuser
> can.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com




pgsql-general by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: log_statement GUC parameter
Next
From: Pól Ua Laoínecháin
Date:
Subject: Re: Partitioning a table by integer value (preferably in place)