Re: Enhance pg_createsubscriber to create required standby.

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Shubham Khanna <khannashubham1197(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Enhance pg_createsubscriber to create required standby.
Date: 2025-06-04 20:20:17
Message-ID: 5cb22010-a972-4a1c-b4d3-7f2250fdb9f9@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04.06.25 11:56, Amit Kapila wrote:
>> It's not clear to me how this change now would substantially improve the
>> user experience. The number of characters you type is approximately the
>> same. You still need to support the old mode because the backup might
>> not come from pg_basebackup.
>
> In the current functionality, the user must first manually create a
> standby or use an existing standby to make it a subscriber. I thought
> saving this step for users would be quite helpful. It also helps
> streamline the process into a single, cohesive workflow.

Unless I'm missing something, doesn't this merely replace

pg_basebackup && pg_createsubscriber

with

pg_createsubscriber --create-standby

I mean, as I'm typing this out, this is literally the same number of
characters. Is the second one easier somehow? It's not clear.

>> And then you'd have the maintenance
>> overhead that every new feature in pg_basebackup would potentially have
>> to be passed through or somehow be integrated into pg_createsubscriber.
>
> I am not so sure about this because we use other utilities like pg_ctl
> in this tool, so same argument could be build for it.

Yes, and we tried really hard to avoid the dependency on pg_ctl, but it
was too hard. (I would entertain patches to get rid of it.)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2025-06-04 20:22:06 Re: proposal: schema variables
Previous Message Peter Eisentraut 2025-06-04 20:15:49 Re: pg_upgrade: warn about roles with md5 passwords