004_timeline_switch TAP test may fail

Sergey Tatarintsev <s.tatarintsev@postgrespro.ru>

From: Sergey Tatarintsev <s.tatarintsev@postgrespro.ru>

To: pgsql-hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-06-16T08:01:15Z

Lists: pgsql-hackers

Attachments

0001-Fix-004_timeline_switch-TAP-test-wait-for-standbys-s.patch (text/x-patch) patch 0001

Hi hackers!

I found that after commit 7185eddf0522b3146ed1ff6e063e8e129e77c706 we 
got little omission
in TAP test 004_timeline_switch:
...
my $node_standby_1 = PostgreSQL::Test::Cluster->new('standby_1');
...
$node_primary->stop;

There is no guarantee that standby_1 and standby_2 was successfully 
connected to primary and start
streaming before primary stopped.

  I think we must ensure that primary knows about standby_1 and standby_2

-- 
With best regards,
Sergey Tatarintsev,
PostgresPro

Commits

Fix another instability in recovery TAP test 004_timeline_switch
- d75146456fa5 14 (unreleased) landed
- e214cf509977 15 (unreleased) landed
- 1316c166faf6 16 (unreleased) landed
- 3afabab78d25 17 (unreleased) landed
- 5a4fea0ce5d9 18 (unreleased) landed
- 9285737ac3cf 19 (unreleased) landed
Fix rare instability in recovery TAP test 004_timeline_switch
- 7185eddf0522 18.4 cited