| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Alena Vinter <dlaaren8(at)gmail(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Ilyasov Ian <ianilyasov(at)outlook(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Resetting recovery target parameters in pg_createsubscriber |
| Date: | 2025-12-03 05:08:12 |
| Message-ID: | aS_FvOYnDCd33Jjl@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-12-03 05:11:39 | Re: Resetting recovery target parameters in pg_createsubscriber |
| Previous Message | Japin Li | 2025-12-03 05:05:51 | Re: Improve pg_sync_replication_slots() to wait for primary to advance |