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

From Marco Nenciarini
Subject Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery
Date
Msg-id CA+nrD2c1Vcz9WPHGK9dORpg86qASk4OaVX9nUJNWk542Ri2SCw@mail.gmail.com
Whole thread Raw
In response to Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery  (Xuneng Zhou <xunengzhou@gmail.com>)
Responses Re: BUG: Cascading standby fails to reconnect after falling back to archive recovery
List 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

pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: tupdesc: simplify assert in equalTupleDescs()
Next
From: Lukas Fittl
Date:
Subject: Re: Stack-based tracking of per-node WAL/buffer usage