Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: Marco Nenciarini <marco(dot)nenciarini(at)enterprisedb(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery
Date: 2026-05-16 07:13:03
Message-ID: CABPTF7WHeqRVH_1dSRRTimUnJp8JMLE05kG2qdd12KU2uaLMag@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 6, 2026 at 7:28 PM Marco Nenciarini
<marco(dot)nenciarini(at)enterprisedb(dot)com> wrote:
>
> Hi Xuneng,
>
> You're right that polling isn't ideal. For a backpatchable bug fix
> though, the trade-off seems reasonable: the change is contained in
> the walreceiver, doesn't touch the wire protocol, and applies to all
> back branches. Exploring better designs would be worthwhile but
> probably belongs in a separate effort.

Yeah, it's still better than remaining unfixed. I'll look into it.

--
Regards,
Xuneng Zhou
HighGo Software Co., Ltd.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-05-16 07:18:05 Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION
Previous Message Mohamed ALi 2026-05-16 06:48:58 [PATCH] Add NESTED_STATEMENTS option to EXPLAIN