From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_log_backend_memory_contexts() and log level |
Date: | 2022-01-26 05:20:53 |
Message-ID: | CALj2ACXmezQKAmXZs3eFPx8S9nk2LuzdvkepcxxNbMSUMjeiSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 26, 2022 at 10:46 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> On Wed, Jan 26, 2022 at 9:48 AM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
> >
> > Hi,
> >
> > pg_log_backend_memory_contexts() should be designed not to send the messages about the memory contexts to the client regardless of client_min_messages. But I found that the message "logging memory contexts of PID %d" can be sent to the client because it's ereport()'d with LOG level instead of LOG_SERVER_ONLY. Is this a bug, and shouldn't we use LOG_SERVER_ONLY level to log that message? Patch attached.
>
> +1. The patch LGTM.
>
> The same applies for the on-going patch [1] for pg_log_backtrace, let
> me quickly send the updated patch there as well.
>
> [1] - https://www.postgresql.org/message-id/CALDaNm3tbc1OKvSKvD5SfmEj66M_sWDPCgDvzFtS9gxRov8jRQ%40mail.gmail.com
My bad, the v17 patch of pg_log_backtrace at [1] does emit at LOG_SERVER_ONLY.
Regards,
Bharath Rupireddy.
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2022-01-26 05:27:00 | Re: pg_log_backend_memory_contexts() and log level |
Previous Message | Bharath Rupireddy | 2022-01-26 05:16:22 | Re: pg_log_backend_memory_contexts() and log level |