Re: pg_createsubscriber --dry-run logging concerns - Mailing list pgsql-hackers

From Peter Smith
Subject Re: pg_createsubscriber --dry-run logging concerns
Date
Msg-id CAHut+Pu84M8tgTjn++4WCTETOX=NR4YmLn-+4B29UJeDTgoJ9Q@mail.gmail.com
Whole thread Raw
In response to Re: pg_createsubscriber --dry-run logging concerns  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: pg_createsubscriber --dry-run logging concerns
List pgsql-hackers
On Wed, Oct 8, 2025 at 9:04 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
>
> On 2025-Oct-08, Peter Smith wrote:
>
> > I am not wedded to doing this double-messaging... if people feel just
> > the one-time logging at the beginning is enough, then that is OK by
> > me.
>
> Some other tools (not Postgres ones) do that and it always makes me
> nervous, because I can never be sure which parts were actually done and
> which parts are only dry-run trials.  I'd rather stay away from that
> approach.
>

OK. Here are v2 patches to implement both ways. You can pick one or both.

0001 - a beginning log to say if the tool is in dry-run mode
0002 - alternate pg_log_info messages for pg_createsubscriber, when in
dry-run mode

~

Note: there might be a clash with another thread [1] if that gets
committed soon; I will deal with any rebase if/when it is needed.

======
[1]
https://www.postgresql.org/message-id/flat/CAHut%2BPv7qDvLbDgc9PQGhULT3rPXTxdu_%3Dw%2BiW-kMs%2BzPADR%2Bw%40mail.gmail.com

Kind Regards,
Peter Smith.
Fujitsu Australia

Attachment

pgsql-hackers by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: another autovacuum scheduling thread
Next
From: David Rowley
Date:
Subject: Re: another autovacuum scheduling thread