diff options
| -rw-r--r-- | src/bin/pg_basebackup/t/040_pg_createsubscriber.pl | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl b/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl index 74b90d9a913..bb121271570 100644 --- a/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl +++ b/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl @@ -227,10 +227,6 @@ command_fails( ], 'primary server is in recovery'); -# Insert another row on node P and wait node S to catch up -$node_p->safe_psql($db1, "INSERT INTO tbl1 VALUES('second row')"); -$node_p->wait_for_replay_catchup($node_s); - # Check some unmet conditions on node P $node_p->append_conf( 'postgresql.conf', q{ @@ -306,6 +302,14 @@ my $result = $node_s->safe_psql('postgres', ); is($result, 'failover_slot', 'failover slot is synced'); +# Insert another row on node P and wait node S to catch up. We +# intentionally performed this insert after syncing logical slot +# as otherwise the local slot's (created during synchronization of +# slot) xmin on standby could be ahead of the remote slot leading +# to failure in synchronization. +$node_p->safe_psql($db1, "INSERT INTO tbl1 VALUES('second row')"); +$node_p->wait_for_replay_catchup($node_s); + # Create subscription to test its removal my $dummy_sub = 'regress_sub_dummy'; $node_p->safe_psql($db1, |