Re: Resetting recovery target parameters in pg_createsubscriber

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Alena Vinter <dlaaren8@gmail.com>

Cc: Alexander Korotkov <aekorotkov@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Ilyasov Ian <ianilyasov@outlook.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2025-12-03T05:08:12Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

pg_createsubscriber: Improve handling of automated recovery configuration
- 639352d904c8 19 (unreleased) landed

On Tue, Nov 25, 2025 at 01:45:56PM +0700, Alena Vinter wrote:
> It seems my previous message isn't visible in the thread. I can see
> Robert's reply, but not the original message he was responding to. I'm
> resending the message and all attachments to ensure it's saved in the
> thread.

I don't understand the fuzziness of the patch around recovery.conf.
Why would that be required knowing that pg_createsubscriber only
supports the same major version as the target server?  We have dropped
support for recovery.conf a long time ago, and this includes all
stable branches.

FWIW, based on the concerns I'm grabbing, nothing presented on this
thread would be candidate material for a backpatch.  Just mentioning
in passing.
--
Michael