Re: BUG: Former primary node might stuck when started as a standby
Alexander Law <exclusion@gmail.com>
From: Alexander Lakhin <exclusion@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
Aleksander Alekseev <aleksander@timescale.com>
Date: 2026-02-12T19:00:00Z
Lists: pgsql-hackers
Attachments
- 099_change_roles.pl (application/x-perl)
Dear Kuroda-san, 09.02.2026 04:38, Hayato Kuroda (Fujitsu) wrote: > > Dear Alexander, Aleksander > > Is it enough that we can wait till all WALs are replayed before the promotion? > > Like attached. > > Thank you for paying attention to this! I tried to add $primary->wait_for_replay_catchup($standby); in my test (see attached), but that doesn't help -- it still fails as below: iteration 61 # +++ tap check in src/test/recovery +++ t/099_change_roles.pl .. 1/? make: *** [Makefile:28: check] Terminated src/test/recovery/tmp_check/log/099_change_roles_node1.log 2026-02-12 20:30:42.953 EET [2716149] LOG: new timeline 4 forked off current database system timeline 3 before current recovery point 0/3025B48 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