Horton
Menu

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

Xuneng Zhou <xunengzhou@gmail.com>

View thread
From: Xuneng Zhou <xunengzhou@gmail.com>
To: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, pgsql-hackers@postgresql.org
Date: 2026-03-17T12:20:42Z
Lists: pgsql-hackers

Attachments

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix scenario where streaming standby gets stuck at a continuation record.

  2. Allow a streaming replication standby to follow a timeline switch.