Re: pg_log_backend_memory_contexts() and log level
От | Bharath Rupireddy |
---|---|
Тема | Re: pg_log_backend_memory_contexts() and log level |
Дата | |
Msg-id | CALj2ACXmezQKAmXZs3eFPx8S9nk2LuzdvkepcxxNbMSUMjeiSw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_log_backend_memory_contexts() and log level (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
Список | pgsql-hackers |
On Wed, Jan 26, 2022 at 10:46 AM Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote: > > On Wed, Jan 26, 2022 at 9:48 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote: > > > > Hi, > > > > pg_log_backend_memory_contexts() should be designed not to send the messages about the memory contexts to the clientregardless of client_min_messages. But I found that the message "logging memory contexts of PID %d" can be sent tothe 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_ONLYlevel 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.
В списке pgsql-hackers по дате отправления: