Re: BUG: Former primary node might stuck when started as a standby
Alexander Law <exclusion@gmail.com>
From: Alexander Lakhin <exclusion@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>,
Aleksander Alekseev <aleksander@timescale.com>
Date: 2026-03-04T09:00:00Z
Lists: pgsql-hackers
04.03.2026 10:23, Michael Paquier wrote: > Did you find any buildfarm failures involving 028? I cannot get > excited in changing tests where nothing has happened, and this test > looks OK as we don't do a switchover. For 004, we have at least one > failure recorded based on what you said. That's a fact sufficient for > me to fix things, for 004. No, I didn't. I agree that eliminating already known failures makes more sense. Anyway, we'll have the thread which explain why such failures can happen. Best regards, Alexander
Commits
-
Fix rare instability in recovery TAP test 004_timeline_switch
- 1346794feb77 14.23 landed
- 270e7b4ff519 15.18 landed
- 8e3c377e284a 16.14 landed
- 6fb8f424be05 17.10 landed
- 7185eddf0522 18.4 landed
- ea4744782b3f 19 (unreleased) landed
-
Fix rare instability in recovery TAP test 009_twophase
- bce98e49e8ac 14.23 landed
- be233b301e60 15.18 landed
- a7499ff5eb58 16.14 landed
- c81b10459bb8 17.10 landed
- 54e0a8fff145 18.4 landed
- ad8c86d22cbd 19 (unreleased) landed