Autofail back inconsistent

From: VASUKI M <vasukim1992002(at)gmail(dot)com>
To: pgpool-general(at)lists(dot)postgresql(dot)org
Cc: bharatdb(at)cdac(dot)in
Subject: Autofail back inconsistent
Date: 2025-10-29 10:09:59
Message-ID: CACTYHzi9=_fM80pWCgGSVmXUdAkMKTpcL5yL28AY67kD32Bn2Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgpool-general

Hi Pgpool-II Community, đź‘‹

I’ve been working on enhancing *Pgpool-II* by introducing a new feature
called *“Automatic Resync and Reattach”*, aimed at improving high
availability and reducing manual intervention after node failures.

This feature automatically performs:

-

*pg_rewind synchronization* and *WAL replay* for failed or lagging
standby nodes
-

*Automatic reattachment* of standby nodes once they are safely resynced

This enhancement overcomes some limitations of the existing:

-

*Online Recovery*, which requires manual pcp_recovery_node execution
-

*Auto Failback*, which may reattach inconsistent nodes without
synchronization

With *Auto Resync & Reattach*, Pgpool-II now ensures data safety and
consistency during failover recovery, providing a more robust
high-availability environment.

I’ve created a dedicated repository with detailed setup instructions,
configuration samples, and diagrams here:
👉 *https://github.com/BharatDBPG/pgpool2-auto-resync
<https://github.com/BharatDBPG/pgpool2-auto-resync>*

The repository includes:

-

Enhanced failover.sh and follow_primary.sh scripts which handles both
primary and standby failure.
-

A new resync.sh script integrating pg_rewind + WAL replay
-

Sample configuration files for a *1 Primary + 2 Standby* setup

I’d love to get feedback from the community
Thanks in advance.

Best regards,
*Vasuki M*
https://github.com/BharatDBPG/pgpool2-auto-resync

Browse pgpool-general by date

  From Date Subject
Previous Message Luca Ferrari 2025-10-29 08:22:39 Re: what is causing different pcp_node_info status