Autofail back inconsistent

Hi Pgpool-II Community,

I’ve been working with PostgreSQL for quite some time, and while managing
backend servers with Pgpool-II, I noticed that there’s no built-in data
synchronization before standby nodes are reattached.

To address this, I’ve developed a new enhancement for Pgpool-II 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 existing features:

-

*Online Recovery* – requires manual execution of pcp_recovery_node
-

*Auto Failback* – may reattach inconsistent nodes without synchronization

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

I’ve created a dedicated GitHub repository with setup instructions,
configuration samples, and architecture diagrams here:
https://github.com/BharatDBPG/pgpool2-auto-resync

The repository includes:

-

Enhanced failover.sh and follow_primary.sh scripts (handling both
primary and standby failures)
-

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

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

I would love to receive feedback or suggestions from the community
regarding possible improvements or integration ideas.

I will be happy to share a patch if needed.
Thank you for your time and support.

Best regards,

*Vasuki MCDAC,CHENNAI*

https://github.com/BharatDBPG/pgpool2-auto-resync