Re: Reduce log level of some logical decoding messages to DEBUG1

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Reduce log level of some logical decoding messages to DEBUG1
Date: 2026-03-25 03:15:22
Message-ID: CAHGQGwFB+hC97SHDpn1vOHHOq9uM5OZZmt50j7v6Z1JUNtH5zQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 24, 2026 at 12:44 AM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> > > Alternatively, if we want to keep them at LOG by default, we could introduce
> > > a GUC like trace_logical_decoding_messages, similar to
> > > the old trace_recovery_messages, to control their verbosity independently
> > > of log_min_messages.

Just in case where many users still want to see those log messages at LOG level,
I also created a second patch (0002) that introduces a new GUC,
trace_logical_decoding_messages, to control logging of logical
decoding debug messages (e.g., "logical decoding found consistent point").

With the default setting (DEBUG1 for now), these messages are effectively
logged at LOG level. Setting it to LOG suppresses them unless permitted
by log_min_messages.

At the moment, this parameter affects only a small set of messages
(about five). We can consider extending it to cover more logical
decoding messages later.

Regards,

--
Fujii Masao

Attachment Content-Type Size
v2-0001-Reduce-log-level-of-some-logical-decoding-message.patch application/octet-stream 3.3 KB
v2-0002-Add-trace_logical_decoding_messages-GUC-to-contro.patch application/octet-stream 9.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-03-25 03:15:32 Re: Test timings are increasing too fast for cfbot
Previous Message Bertrand Drouvot 2026-03-25 03:15:19 Re: Adding locks statistics