Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery - Mailing list pgsql-hackers

From Xuneng Zhou
Subject Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery
Date
Msg-id CABPTF7WOj=HCB6zoY2Uked5gK5ywNdKw-d_10DMEFaRg-dHBSA@mail.gmail.com
Whole thread
In response to Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery  (Marco Nenciarini <marco.nenciarini@enterprisedb.com>)
Responses Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery
List pgsql-hackers
On Tue, Mar 17, 2026 at 7:56 PM Marco Nenciarini
<marco.nenciarini@enterprisedb.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

pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: [Proposal] Adding Log File Capability to pg_createsubscriber
Next
From: Alexandre Felipe
Date:
Subject: Re: New access method for b-tree.