Re: Resetting recovery target parameters in pg_createsubscriber

From: Alena Vinter <dlaaren8(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andrey Rudometov <unlimitedhikari(at)gmail(dot)com>, 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-30 07:34:21
Message-ID: CAGWv16KkTVZhULD1JAgqqORhfZxUH-kSEHvR16KO5gqJEOd9Tw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi everyone!

Apologies for the long silence — I was temporarily pulled away from this
work and didn’t want to send an update until I could properly address the
feedback.

I’m now back on track and have refined the implementation based on earlier
discussions. The current version fully adopts the `include_if_exists`
approach, writes temporary recovery settings to a separate config file, and
disables it on exit by renaming to `.disabled`.

Thank you for your patience — I appreciate any further review!

---
Alena Vinter

Attachment Content-Type Size
v9-0001-pg_createsubscriber-use-include_if_exists-for-recove.patch text/x-patch 6.5 KB
v9-0002-Doc-configuration-file-handling-in-pg_createsubscrib.patch text/x-patch 2.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-12-30 07:44:03 Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Previous Message Chao Li 2025-12-30 07:17:26 Re: Refactor replication origin state reset helpers