Re: pg_log_backend_memory_contexts() and log level

Поиск
Список
Период
Сортировка
От Bharath Rupireddy
Тема Re: pg_log_backend_memory_contexts() and log level
Дата
Msg-id CALj2ACXSuCiEAXqgk0CzbPwKghB5UBrR+YhPZfgjYtGf2mMtYQ@mail.gmail.com
обсуждение исходный текст
Ответ на pg_log_backend_memory_contexts() and log level  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Ответы Re: pg_log_backend_memory_contexts() and log level  (Bharath Rupireddy <bharath.rupireddyforpostgres@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 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 client
regardlessof client_min_messages. But I found that the message "logging memory contexts of PID %d" can be sent to the
clientbecause 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. The pg_log_query_plan
on-going patch [2], does the right thing.

[1] - https://www.postgresql.org/message-id/CALDaNm3tbc1OKvSKvD5SfmEj66M_sWDPCgDvzFtS9gxRov8jRQ%40mail.gmail.com
[2] - https://www.postgresql.org/message-id/fb6360e4c0ffbdd0a6698b92bb2617e2%40oss.nttdata.com

Regards,
Bharath Rupireddy.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Skipping logical replication transactions on subscriber side
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: pg_log_backend_memory_contexts() and log level