mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix random failure in 004_subscription.

Browse Source 
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
This commit is contained in:
Amit Kapila 2024-03-27 14:15:03 +05:30
parent 6d49c8d4b4
commit 677a45c4ae
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/bin/pg_upgrade/t/004_subscription.pl
View File

@ -314,6 +314,9 @@ $new_sub->restart;
$new_sub->safe_psql('postgres', "ALTER SUBSCRIPTION regress_sub5 ENABLE"); $new_sub->safe_psql('postgres', "ALTER SUBSCRIPTION regress_sub5 ENABLE");
$new_sub->wait_for_subscription_sync($publisher, 'regress_sub5'); $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 # Rows on tab_upgraded1 and tab_upgraded2 should have been replicated
$result = $result =
$new_sub->safe_psql('postgres', "SELECT count(*) FROM tab_upgraded1"); $new_sub->safe_psql('postgres', "SELECT count(*) FROM tab_upgraded1");