Commitc71f9a0

committed

Make pg_rewind test case more stable.

If replication is exceptionally slow for some reason, pg_rewind might runbefore the test row has been replicated. Add an explicit wait for it.Reported-by: Andres FreundDiscussion:https://www.postgresql.org/message-id/20201120003811.iknhqwatitw2vvxf%40alap3.anarazel.de

1 parent16f96c7 commitc71f9a0Copy full SHA for c71f9a0

File tree

-0

lines changed

-0

lines changed

Lines changed: 4 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -89,6 +89,10 @@`
`89`	`89`	`$node_a->safe_psql('postgres',`
`90`	`90`	`"INSERT INTO tbl1 VALUES ('in A, after C was promoted')");`
`91`	`91`
	`92`	`+# make sure it's replicated to B before we continue`
	`93`	`+$lsn =$node_a->lsn('insert');`
	`94`	`+$node_a->wait_for_catchup('node_b','replay',$lsn);`
	`95`	`+`
`92`	`96`	`# Also insert a new row in the standby, which won't be present in the`
`93`	`97`	`# old primary.`
`94`	`98`	`$node_c->safe_psql('postgres',`

Comments

(0)