Re: duplicate logging in pg_createsubscriber - Mailing list pgsql-hackers

From Chao Li
Subject Re: duplicate logging in pg_createsubscriber
Date
Msg-id 83BE4BD6-DDCC-461A-A038-EBFB4A03B537@gmail.com
Whole thread Raw
In response to duplicate logging in pg_createsubscriber  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: duplicate logging in pg_createsubscriber
List pgsql-hackers


On Oct 8, 2025, at 14:29, Peter Smith <smithpb2250@gmail.com> wrote:

Perhaps that 2nd log was once supposed to say "created" (past tense),
but even that seemed redundant.

Here is a small patch to remove the log duplication by keeping only
the log *within* the function.

Thoughts?

======
Kind Regards,
Peter Smith.
Fujitsu Asutralia
<v1-0001-remove-duplicate-logging-for-slot-creation.patch>

The change is straightforward, especially I like the second change of adding “on publisher”, which makes the message clearer.

For dry-run mode, I see in setup_recovery(), it debug-logs a message with “# dry run mode recovery_target_lsn = xxx”, I think it would be good to add similar debug logs in create_logical_replication_slot(), create_publication() and drop_publication().

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/




pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE
Next
From: Peter Smith
Date:
Subject: Re: duplicate logging in pg_createsubscriber