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 1vE60Z-004kZs-8E for pgpool-general@arkaria.postgresql.org; Wed, 29 Oct 2025 13:14:34 +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 1vE60Y-0016Ab-66 for pgpool-general@arkaria.postgresql.org; Wed, 29 Oct 2025 13:14:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vE37f-00HItq-Ip for pgpool-general@lists.postgresql.org; Wed, 29 Oct 2025 10:09:42 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vE37c-004MO7-22 for pgpool-general@lists.postgresql.org; Wed, 29 Oct 2025 10:09:41 +0000 Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-b6d3340dc2aso244070166b.0 for ; Wed, 29 Oct 2025 03:09:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1761732579; x=1762337379; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=NH9/AbLmAb5OzMNocYRfx3bS0qaVd+/7OyNvDr8hpE0=; b=ameOd75JcbVvIwQjad5J3NsNgSOhs+p4giP4rtYqi2onGBj9o52mOa+wjOUxMpaywd wZkVxhQXqOLpNczxBjL6XHtplHhSLP8jrMr8/YNwyLDpnYFi49K/WT+lGoUiAlNUgDMw 2cdAu989VQyQ0hModwAccl0BWBElqGMr4TLk/afkv1nnp6FtlMSWhUvtI67Rb8GBWxyW GxtYz+LSaz4bavOk9Xr0na0bpJNW2Adj9LFCp97IgHSJ3VLYhKZtGZwwHTBbKrsz42xk d6AgRhA+4CHR1SVkxcghhfU5qKP6Z3QLdXzlVdKhjwHL2B+/xe64D48wTQ7YInLFjCvY Lnow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761732579; x=1762337379; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=NH9/AbLmAb5OzMNocYRfx3bS0qaVd+/7OyNvDr8hpE0=; b=r8bhKzASOHqTCK9eeo/ZuKv2EZM4yaobGcJHr+1e4JUhFwVte9tu0vbHk3B9MKiHf9 m5XoBpp4ltfZCJUymGydRPtJzT7Q0O404wZj7Q6Saby+SjDeu61FaPBvYSWDRV5l6Ytu gLMfE8aMKpiLSBC6cVwpgGr6InMm4kRbtHCKGfN4/QcoF1sVPXdzRYoFK2WtfAr7GPPj 8P9JZZNoJJPwTsUXhrIHpr90KX6fAeD85uVT8hMhRw8n80kZ/IvWrKtSWPIVGSUzTCJR PMRnkn2Xu4+ieBCiJ+/IXmXuE8byeAY8cydRPokkHhynhPjVZjtcZW6HBCe4/5N736Ez Ulvw== X-Gm-Message-State: AOJu0YykeZXBLJ/MB3UAR7w4jJtY9y+6G9AOgSempja0MsJFFdzbG12v orx8ijqqM6W4XNPza0Jr5PBRa62MdvRegU+rjmoSCoR5mKjAc6/9qTkud/g3IrEusStxwr0vxTd atwGyOdxaR3v/rtyaSJzyYudvCftqbYYYxHNL X-Gm-Gg: ASbGnctisdJVJSaX5KRKdlkzaINJYAjjiKHABpwDmlUB6RafgjLarEveZ6/r7qOLnhj LGYycMUE+FuTR+fSmFIG4S7hBIZlA/ZxqwMUDogP8tgweJygClIlp66UQBtW2RAO+FJDJYS5lS2 Yq7Oe7qy60kmgPCDd0qVeuW7gixqcY+3YRBPGPSdjbnZDH+J/vTLKnCG91jgqYxlLHlF7bJoMtC +Gh24OOWHI3tyzGYPCmSH1YWm8uNgpA87qPxXXamOlulZ1fIMri4LjXKFa7 X-Google-Smtp-Source: AGHT+IHf+i6jCsdxcwVFoQBGO2dRv84lx5r+7qBJa4daFYMtVtaMXLIESGFTCnPlRnU7MSdisgFJBR2c9/PKvkMf+P8= X-Received: by 2002:a17:907:7203:b0:b6d:3456:14b3 with SMTP id a640c23a62f3a-b6dbbfb8357mr643710466b.20.1761732578464; Wed, 29 Oct 2025 03:09:38 -0700 (PDT) MIME-Version: 1.0 From: VASUKI M Date: Wed, 29 Oct 2025 15:39:59 +0530 X-Gm-Features: AWmQ_blxoY7BMErx47JJe3ZRBbkUJDjSFAyyvIK8dTslJ3jsS1gPJWT7sJhooSY Message-ID: Subject: Autofail back inconsistent To: pgpool-general@lists.postgresql.org Cc: bharatdb@cdac.in Content-Type: multipart/alternative; boundary="0000000000008756060642495427" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008756060642495427 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Pgpool-II Community, =F0=9F=91=8B I=E2=80=99ve been working on enhancing *Pgpool-II* by introducing a new fea= ture called *=E2=80=9CAutomatic Resync and Reattach=E2=80=9D*, aimed at improvin= g 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=E2=80=99ve created a dedicated repository with detailed setup instruction= s, configuration samples, and diagrams here: =F0=9F=91=89 *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=E2=80=99d love to get feedback from the community Thanks in advance. Best regards, *Vasuki M* https://github.com/BharatDBPG/pgpool2-auto-resync --0000000000008756060642495427 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Pgpool-II Community, =F0=9F=91=8B

I=E2=80=99ve been working on enhancing Pgpool-II by int= roducing a new feature called =E2=80=9CAutomatic Resync and Reattac= h=E2=80=9D, aimed at improving high availability and reducing manu= al 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 the existing:

  • Online Recovery, which requires manual pcp_recove= ry_node execution

  • Auto Failback, which may reattach inconsistent nodes wi= thout synchronization

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

I=E2=80=99ve created a dedicated repository with detailed setup instruct= ions, configuration samples, and diagrams here:
=F0=9F=91=89 https://github.com/BharatDBPG/pgpool2-auto-resync

The repository includes:

  • Enhanced failover.sh and follow_primary.sh scr= ipts 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=E2=80=99d love to get feedback from the community=C2=A0
Thanks in a= dvance.

Best regards,
Vasuki M
https://githu= b.com/BharatDBPG/pgpool2-auto-resync

--0000000000008756060642495427--