Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit0324651

Browse files
author
Amit Kapila
committed
Fix the test case introduced by commit8756930.
Before dropping a relation, ensure that it has reached a 'ready' stateafter initial synchronization.Author: Vignesh CReviewed-By: Amit KapilaDiscussion:https://www.postgresql.org/message-id/CALDaNm0gwjY_4HFxvvty01BOT01q_fJLKQ3pWP9=9orqubhjcQ@mail.gmail.com
1 parent8756930 commit0324651

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

‎src/test/subscription/t/030_origin.pl

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,13 @@
195195
"Refresh publication when the publisher has subscribed for the new table, but the subscriber-side wants origin = none"
196196
);
197197

198-
$node_A->wait_for_subscription_sync($node_B,$subname_AB2);
198+
# Ensure that relation has reached 'ready' state before we try to drop it
199+
my$synced_query =
200+
"SELECT count(1) = 0 FROM pg_subscription_rel WHERE srsubstate NOT IN ('r');";
201+
$node_A->poll_query_until('postgres',$synced_query)
202+
ordie"Timed out while waiting for subscriber to synchronize data";
203+
204+
$node_B->wait_for_catchup($subname_AB2);
199205

200206
# clear the operations done by this test
201207
$node_A->safe_psql('postgres',"DROP TABLE tab_new");

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp