aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2024-03-27 14:15:03 +0530
committerAmit Kapila <akapila@postgresql.org>2024-03-27 14:15:03 +0530
commit677a45c4ae165f86b4a7b8562795f19f1ed480cf (patch)
treee0b42ceef43819bb2cf9a70a47e2cd6ee8901416 /src
parent6d49c8d4b4f4a20eb5b4c501d78cf894fa13c0ea (diff)
downloadpostgresql-677a45c4ae165f86b4a7b8562795f19f1ed480cf.tar.gz
postgresql-677a45c4ae165f86b4a7b8562795f19f1ed480cf.zip
Fix random failure in 004_subscription.
After the upgrade, the failed test was ensuring that the changes made on the publisher should be replicated to the subscriber. We missed waiting for one of the subscriptions to catch up. Per buildfarm Author: Vignesh C Reviewed-by: Kuroda Hayato Discussion: https://postgr.es/m/CALDaNm0z=fLtio1h50K8WossUGXU+gy0H9y9=RYh1DDZiq2EDw@mail.gmail.com
Diffstat (limited to 'src')
-rw-r--r--src/bin/pg_upgrade/t/004_subscription.pl3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/bin/pg_upgrade/t/004_subscription.pl b/src/bin/pg_upgrade/t/004_subscription.pl
index df5d6dffbc3..48918e8c294 100644
--- a/src/bin/pg_upgrade/t/004_subscription.pl
+++ b/src/bin/pg_upgrade/t/004_subscription.pl
@@ -314,6 +314,9 @@ $new_sub->restart;
$new_sub->safe_psql('postgres', "ALTER SUBSCRIPTION regress_sub5 ENABLE");
$new_sub->wait_for_subscription_sync($publisher, 'regress_sub5');
+# wait for regress_sub4 to catchup as well
+$publisher->wait_for_catchup('regress_sub4');
+
# Rows on tab_upgraded1 and tab_upgraded2 should have been replicated
$result =
$new_sub->safe_psql('postgres', "SELECT count(*) FROM tab_upgraded1");