database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-08 06:02:22 +03:00
Code Activity

Make pg_rewind test case more stable.

Browse Source 
If replication is exceptionally slow for some reason, pg_rewind might run
before the test row has been replicated. Add an explicit wait for it.

Reported-by: Andres Freund
Discussion: https://www.postgresql.org/message-id/20201120003811.iknhqwatitw2vvxf%40alap3.anarazel.de
This commit is contained in:
Heikki Linnakangas
2020-11-20 16:08:58 +02:00
parent 16f96c74d4
commit c71f9a094b
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/bin/pg_rewind/t/007_standby_source.pl
View File

@@ -89,6 +89,10 @@ $node_c->safe_psql('postgres', "checkpoint");
$node_a->safe_psql('postgres', $node_a->safe_psql('postgres',
"INSERT INTO tbl1 VALUES ('in A, after C was promoted')"); "INSERT INTO tbl1 VALUES ('in A, after C was promoted')");
# make sure it's replicated to B before we continue
$lsn = $node_a->lsn('insert');
$node_a->wait_for_catchup('node_b', 'replay', $lsn);
# Also insert a new row in the standby, which won't be present in the # Also insert a new row in the standby, which won't be present in the
# old primary. # old primary.
$node_c->safe_psql('postgres', $node_c->safe_psql('postgres',