Re: duplicate logging in pg_createsubscriber

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: duplicate logging in pg_createsubscriber
Date: 2025-10-09 02:30:59
Message-ID: 83BE4BD6-DDCC-461A-A038-EBFB4A03B537@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Oct 8, 2025, at 14:29, Peter Smith <smithpb2250(at)gmail(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-10-09 02:36:36 Re: duplicate logging in pg_createsubscriber
Previous Message Hayato Kuroda (Fujitsu) 2025-10-09 02:28:56 RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE