| From: | Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: log_statement GUC parameter |
| Date: | 2021-08-12 20:51:33 |
| Message-ID: | 4534f313-b374-2dc4-d0a4-5d301981a089@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pól Ua Laoínecháin | 2021-08-13 06:50:40 | Re: Partitioning a table by integer value (preferably in place) |
| Previous Message | Mladen Gogala | 2021-08-12 20:49:00 | Re: log_statement GUC parameter |