public inbox for [email protected]  

help / color / mirror / Atom feed

From: VASUKI M <[email protected]>
To: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Automating Failover Resync & Re-Attach in pgpool2
Date: Fri, 10 Oct 2025 17:47:09 +0530
Message-ID: <CACTYHzgopGRZmWeWPLXKw=McAQigLC51+mqsmyULypKhfMSJ_w@mail.gmail.com> (raw)

Dear PostgreSQL and Pgpool Communities,

While working with PostgreSQL failover scenarios, I noticed that the
process of re-attaching a standby node after a failover can be somewhat
manual and prone to delays, especially in production environments.

I explored automating this process using a combination of *pg_rewind* and *WAL
replay*, which allows a standby node to resynchronize and re-attach to the
primary automatically after a failover. This could reduce downtime and
simplify management of failover nodes in high-availability setups.

Automatically resynchronize after failover

Reduce downtime and ensure quicker recovery

Minimize manual operations and errors

Maintain consistent cluster state with less administrative overhead

I believe that integrating such an automated resync and re-attach feature
into *Pgpool-II* could be very valuable for PostgreSQL users, potentially
as an enhancement in a future release.

I wanted to share this idea with the community to get feedback,
suggestions, or any pointers on existing work that may align with this. I
am happy to contribute more details

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Automating Failover Resync & Re-Attach in pgpool2
  In-Reply-To: <CACTYHzgopGRZmWeWPLXKw=McAQigLC51+mqsmyULypKhfMSJ_w@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox