Re: Enhance pg_createsubscriber to create required standby. - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Enhance pg_createsubscriber to create required standby.
Date
Msg-id CAKFQuwa4aR4vzvbGikiLLGnh-pkPDMRCh4jSL_D72vGJJVUK=A@mail.gmail.com
Whole thread Raw
In response to Re: Enhance pg_createsubscriber to create required standby.  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tue, Jun 17, 2025 at 9:22 PM Amit Kapila <amit.kapila16@gmail.com> wrote:

As shown in Vignesh's email [1] (point 4), there could be multiple
additional parameters required for the first option suggested by you,
which will make it longer. Additionally, there are some other benefits
of having the second option (pg_createsubscriber --create-standby),
like better cleanup of contents during failures and better progress
reporting. Are you still against adding such an option?

[1]: https://www.postgresql.org/message-id/CALDaNm1biZBMOzFMfHYzqrAeosJSD5YRG%3D82-pp6%2BJhALsfe6w%40mail.gmail.com


None of those benefits convince me that "let's write a shell script in C and put it under an annual feature release policy" is the way to go here.

Let's make something like this available to the community, say on the Wiki, and make it work in PostgreSQL 18 so they can benefit from it today, and readily use it as a basis to tweak things for their own unique circumstances.

David J.

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.
Next
From: Peter Eisentraut
Date:
Subject: Re: minimum Meson version