MIME-Version: 1.0
From: VASUKI M <vasukim1992002@gmail.com>
Date: Fri, 10 Oct 2025 17:47:09 +0530
Message-ID: 
 <CACTYHzgopGRZmWeWPLXKw=McAQigLC51+mqsmyULypKhfMSJ_w@mail.gmail.com>
Subject: Automating Failover Resync & Re-Attach in pgpool2
To: pgsql-bugs@lists.postgresql.org
Cc: bharatdb@cdac.in, pgpool-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000002df7f10640cce4bd"
Archived-At: 
 <https://www.postgresql.org/message-id/CACTYHzgopGRZmWeWPLXKw%3DMcAQigLC51%2BmqsmyULypKhfMSJ_w%40mail.gmail.com>
Precedence: bulk

--0000000000002df7f10640cce4bd
Content-Type: text/plain; charset="UTF-8"

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

--0000000000002df7f10640cce4bd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>Dear PostgreSQL and Pgpool Communities,</p>
<p>While working with PostgreSQL failover scenarios, I noticed that the pro=
cess of re-attaching a standby node after a failover can be somewhat manual=
 and prone to delays, especially in production environments.</p>
<p>I explored automating this process using a combination of <strong><code>=
pg_rewind</code></strong> and <strong>WAL replay</strong>, which allows a s=
tandby node to resynchronize and re-attach to the primary automatically aft=
er a failover. This could reduce downtime and simplify management of failov=
er nodes in high-availability setups.</p><p>Automatically resynchronize aft=
er failover</p><p>Reduce downtime and ensure quicker recovery</p><p>Minimiz=
e manual operations and errors</p><p>Maintain consistent cluster state with=
 less administrative overhead</p>
<p>I believe that integrating such an automated resync and re-attach featur=
e into <strong>Pgpool-II</strong> could be very valuable for PostgreSQL use=
rs, potentially as an enhancement in a future release.</p>
<p>I wanted to share this idea with the community to get feedback, suggesti=
ons, or any pointers on existing work that may align with this. I am happy =
to contribute more details</p></div>

--0000000000002df7f10640cce4bd--