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-03-17 12:20:42
Message-ID: CABPTF7WOj=HCB6zoY2Uked5gK5ywNdKw-d_10DMEFaRg-dHBSA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 17, 2026 at 7:56 PM Marco Nenciarini
<marco(dot)nenciarini(at)enterprisedb(dot)com> wrote:
>
> Thanks for verifying the fix and improving the test, Xuneng.
>
> The wait_for_event() synchronization is a nice addition — it gives
> deterministic proof that the walreceiver actually entered the
> upstream-catchup path. The scoped log window with slurp_file() is
> also cleaner than the broad log_contains() I had before.
>
> The v3 test improvements look good to me.
>
> Best regards,
> Marco

Thanks for checking. I think we also need to add the new tap test to
meson.build for the master patch as well.

--
Best,
Xuneng

Attachment Content-Type Size
v3-0001-Fix-cascading-standby-reconnect-failure-after-arc.patch application/octet-stream 15.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexandre Felipe 2026-03-17 12:37:47 Re: New access method for b-tree.
Previous Message Hayato Kuroda (Fujitsu) 2026-03-17 12:18:41 RE: [Proposal] Adding Log File Capability to pg_createsubscriber