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

From: Marco Nenciarini <marco(dot)nenciarini(at)enterprisedb(dot)com>
To: Xuneng Zhou <xunengzhou(at)gmail(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 11:55:53
Message-ID: CA+nrD2ex-3KMAmTinGM+Wbaxs30gNNGxt5jeqhBzA-VoSOQQ_Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-03-17 11:58:05 Re: Better shared data structure management and resizable shared data structures
Previous Message Heikki Linnakangas 2026-03-17 11:45:20 Re: Changing the state of data checksums in a running cluster