Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vGBBu-009Qfy-ER for pgpool-hackers@arkaria.postgresql.org; Tue, 04 Nov 2025 07:10:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vGBBt-00BgmQ-Bp for pgpool-hackers@arkaria.postgresql.org; Tue, 04 Nov 2025 07:10:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vG9W9-00B520-32 for pgpool-hackers@lists.postgresql.org; Tue, 04 Nov 2025 05:23:40 +0000 Received: from mail-ed1-x530.google.com ([2a00:1450:4864:20::530]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vG9W5-005sF2-29 for pgpool-hackers@lists.postgresql.org; Tue, 04 Nov 2025 05:23:39 +0000 Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-640c3940649so2670085a12.1 for ; Mon, 03 Nov 2025 21:23:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762233816; x=1762838616; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=iRDCYGlEggol5Iy5Z7+EmcjSx38bo8pOJwPpSGrXCEA=; b=RFpyG/fVB7Y2mxf1nGkfDTvtIIPOKRAP2WzUuoUHvGIb6vgncQpifUP4uMUxuRrnCt tDtNPbBbqNk4AEHgsWk9I6NiSa2JaIk+CW7m3mx22qf7DyH2FWcaXOtRhLswnpw0juXi 5MVqZt+B9a4qfy50fyz5Ol8eeKLQXbLHv9EKeW18/h5f0wxKqfcpI2Epw3TTYBrMrvgW ZjScCF0zLOhqtmbE2/yVZ9PY4AhCdR/7vmYggs1VCfQ5wb1tjQ8Qj51gY9bLsX5QDBi4 J4Cf1X3E9vQpxUINfRlIdVwYhW7UHZtfhjwKUPGWJG2YLvnCIFjHik4xPhugaNbi5GXY bhLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762233816; x=1762838616; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=iRDCYGlEggol5Iy5Z7+EmcjSx38bo8pOJwPpSGrXCEA=; b=SW3r0dqLkufUg84pF9SNBp73YTIhVIV3HeeWkY1xHIKtRKXWgQWXEdaOlTwlAp4ENi QeIwbwDdGfVzgx98dSb1Is1UIdqELhVQTUglohLDioLEwXvb9NHpuLMt7EygfEGzCZGd cLP9yCACQGS39DUWgFK6Nsru3LCQ/LIm9vk424Q1pvF+TUWAySXV07ifZ87uG0p78puJ /k1wwB1i/wWtaxMzZ8bkwAtiFBPL0BM1TGWucbpGW59u0kemLA+RxLXmF3pCrbLKN9lP fViM3zTaWESxtQr4e9Y8vz6d8ou3tqAgHwDvzK8Ge2Zb3VPM2YgJolplKDNCo3a6Bjla NGnQ== X-Gm-Message-State: AOJu0YxWrWCp38dNHMhHFhNeZ0kQQP4XGYkD0XMA+ak3IuZUVhdkXBaD EBoMCrxpxA0sxkooIaX6GJGXtU7frzaDHQow+gtUiWhKWZhdNhQARjKbUVIzbesoLWD6zgdZRWn fcddxsDL/vzhHLRGUzTb/k8sCDuc4HpM= X-Gm-Gg: ASbGncu23EcysZ2jodMJWSlc68v04ZXOc7ZLgoKOpxcCvsudEC+/676g+2eueTXPwZS Ljd7gM3E9wP5dsKGaxiRElZjF0OjZDBdHgh2Tun4inUuoDWm2mQVaAEY+yMslnv5Br9ldXEYtPM pjdRZ9hhZfUu6x0R/XWWDf0icQPks7rQ5KTDBsOqhMRXK9MgcEAdPrJsHPnYuNLDWKKHIeO1Qi2 wy+b7S7n9QDf2rtwD7J2ez0XP/fTaj1BsZBSsml6w1jxb8mJ2aj76pAsCSG X-Google-Smtp-Source: AGHT+IHKO54mXLB2g/N+MTRQvb8dnXPJrhk92tqMK0S19D0XEzMSpEn/OAZe7sBp6a1EJJCKZL7n64KsKXfYr1dYHwo= X-Received: by 2002:a17:907:c24c:b0:b70:ae6a:5fdb with SMTP id a640c23a62f3a-b70ae6a6b41mr677361066b.45.1762233815952; Mon, 03 Nov 2025 21:23:35 -0800 (PST) MIME-Version: 1.0 From: VASUKI M Date: Tue, 4 Nov 2025 10:53:56 +0530 X-Gm-Features: AWmQ_bmlCzVvkdfCiE6AHTJZDttlX0pPFGRspdb0ge5FKjGFvc5SttZCJAtQtuc Message-ID: Subject: Autofail back inconsistent To: ishii@postgresql.org, Bo Peng Cc: pgpool-hackers@lists.postgresql.org, bharatdb@cdac.in Content-Type: multipart/alternative; boundary="0000000000009c70a40642be0800" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009c70a40642be0800 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Pgpool-II Community, I=E2=80=99ve been working with PostgreSQL for quite some time, and while ma= naging backend servers with Pgpool-II, I noticed that there=E2=80=99s no built-in = data synchronization before standby nodes are reattached. To address this, I=E2=80=99ve developed a new enhancement for Pgpool-II cal= led *=E2=80=9CAutomatic Resync and Reattach=E2=80=9D*, aimed at improving high availability and red= ucing 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* =E2=80=93 requires manual execution of pcp_recovery_no= de - *Auto Failback* =E2=80=93 may reattach inconsistent nodes without synchr= onization With *Auto Resync & Reattach*, Pgpool-II ensures data safety and consistency during failover recovery, providing a more robust and self-healing HA environment. I=E2=80=99ve 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 --0000000000009c70a40642be0800 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Pgpool-II Community,

I=E2=80=99ve been working= with PostgreSQL for quite some time, and while managing backend servers wi= th Pgpool-II, I noticed that there=E2=80=99s no built-in data synchronizati= on before standby nodes are reattached.

To address this, I=E2=80=99ve= developed a new enhancement for Pgpool-II called =E2=80=9CAutomati= c Resync and Reattach=E2=80=9D, aimed at improving high availabili= ty 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 s= afely resynced

This enhancement overcomes some limitations of existing features:

  • Online Recovery =E2=80=93 requires manual execution of = pcp_recovery_node

  • Auto Failback =E2=80=93 may reattach inconsistent nodes= without synchronization

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

I=E2=80=99ve created a dedicated GitHub repository with setup instru= ctions, configuration samples, and architecture diagrams here:
=C2=A0https://github.com/BharatDBPG/pgpool2-auto-= resync

The repository includes:

  • Enhanced failover.sh and follow_primary.sh scr= ipts (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 M
CDAC,CHENNAI

https://github.com/BharatDBPG/pgpool2-au= to-resync

--0000000000009c70a40642be0800--