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 08:12:50
Message-ID: CA+nrD2c1Vcz9WPHGK9dORpg86qASk4OaVX9nUJNWk542Ri2SCw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I agree, a standalone test file is the right call here.

I looked at the same candidates. 025_stuck_on_old_timeline.pl is the
closest thematic match, but its archive command intentionally copies
only history files and the whole test revolves around promotion and
timeline following. Adapting it would mean replacing the archive
command and skipping the promotion, which defeats its original purpose.

The reconnect-after-archive-fallback scenario is distinct enough to
justify its own file, and at 143 lines it's reasonably small.

Best regards,
Marco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lukas Fittl 2026-03-17 08:18:38 Re: Stack-based tracking of per-node WAL/buffer usage
Previous Message Nazir Bilal Yavuz 2026-03-17 08:12:45 Re: tupdesc: simplify assert in equalTupleDescs()