1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix the test case introduced by commit 8756930190.

Browse Source 
Before dropping a relation, ensure that it has reached a 'ready' state
after initial synchronization.

Author: Vignesh C
Reviewed-By: Amit Kapila
Discussion: https://www.postgresql.org/message-id/CALDaNm0gwjY_4HFxvvty01BOT01q_fJLKQ3pWP9=9orqubhjcQ@mail.gmail.com
This commit is contained in:
Amit Kapila 2022-09-08 09:47:43 +05:30
parent 8756930190
commit 0324651573
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/test/subscription/t/030_origin.pl
View File

@ -195,7 +195,13 @@ like(
"Refresh publication when the publisher has subscribed for the new table, but the subscriber-side wants origin = none"
);
$node_A->wait_for_subscription_sync($node_B, $subname_AB2);
# Ensure that relation has reached 'ready' state before we try to drop it
my $synced_query =
"SELECT count(1) = 0 FROM pg_subscription_rel WHERE srsubstate NOT IN ('r');";
$node_A->poll_query_until('postgres', $synced_query)
or die "Timed out while waiting for subscriber to synchronize data";
$node_B->wait_for_catchup($subname_AB2);
# clear the operations done by this test
$node_A->safe_psql('postgres', "DROP TABLE tab_new");