| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unfiltered server logs routing via a new elog hook or existing emit_log_hook bypassing log_min_message check |
| Date: | 2022-05-02 14:07:48 |
| Message-ID: | 1833132.1651500468@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> On Mon, May 02, 2022 at 07:24:04PM +0530, Bharath Rupireddy wrote:
>> I basically want to avoid normal users/developers setting any
>> parameter (especially the superuser-only log_min_message GUC, all
>> users might not have superuser access in production environments) or
>> making any changes to the running server except just LOADing the
>> server log routing/intercepting extension.
> The kind of scenario you mentioned didn't seem "normal users" oriented. Note
> that LOAD is restricted to superuser anyway.
It seems completely silly to be worrying that setting a GUC in a
particular way is too hard for somebody who's going to be installing
a loadable extension. In any case, if you wanted to force the issue
you could set log_min_messages in the extension's _PG_init function.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2022-05-02 14:08:31 | Re: strange slow query - lost lot of time somewhere |
| Previous Message | Tom Lane | 2022-05-02 14:03:58 | Re: configure openldap crash warning |