On Tue, Mar 24, 2026 at 12:44 AM Fujii Masao <[email protected]> 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
v2-0001-Reduce-log-level-of-some-logical-decoding-message.patch
Description: Binary data
v2-0002-Add-trace_logical_decoding_messages-GUC-to-contro.patch
Description: Binary data
