On Wed, Oct 8, 2025 at 9:04 PM Álvaro Herrera <[email protected]> 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
v2-0001-log-to-say-command-is-executing-in-dry-run-mode.patch
Description: Binary data
v2-0002-add-different-dry-run-logging-for-pg_createsubscr.patch
Description: Binary data
