]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Reduce log level of some logical decoding messages from LOG to DEBUG1
authorFujii Masao <fujii@postgresql.org>
Wed, 1 Apr 2026 06:43:02 +0000 (15:43 +0900)
committerFujii Masao <fujii@postgresql.org>
Wed, 1 Apr 2026 06:43:02 +0000 (15:43 +0900)
commit21b018e7eab57b5e4be183133a8c5b8229eccb3d
tree2924f0d18f5a4f7163386afb917b8f11c0d4ed94
parent76f4b92bac87fa54bd6dd8bd53e59f93127ec2ef
Reduce log level of some logical decoding messages from LOG to DEBUG1

Previously some logical decoding messages (e.g., "logical decoding found
consistent point") were logged at level LOG, even though they provided
low-level, developer-oriented information that DBAs were typically not
interested in.

Since these messages can occur routinely (for example, when keeping calling
pg_logical_slot_get_changes() to obtain the changes from logical decoding),
logging them at LOG can be overly verbose.

This commit reduces their log level to DEBUG1 to avoid unnecessary log noise.

This change applies to a small set of messages for now. Additional messages
may be adjusted similarly in the future.

Even with this change, if these messages from walsender still need to be
observed, enabling DEBUG1 logging selectively for walsender (e.g.,
log_min_messages = 'warning,walsender:debug1') would be helpful to avoid
increasing overall log volume.

Author: Fujii Masao <masao.fujii@gmail.com>
Reviewed-by: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Discussion: https://postgr.es/m/CAHGQGwGTyHgtD9tyN664x6vQ8Q1G53H7ZUCgBU9_X=nLt3f1QA@mail.gmail.com
src/backend/replication/logical/logical.c
src/backend/replication/logical/snapbuild.c
src/test/recovery/t/038_save_logical_slots_shutdown.pl