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

Commit364298b

Browse files
committed
Fix race condition in recently-added TAP test for recovery consistency
A couple of queries are run on the primary to create and fill in a testtable, which gets checked on the standby afterwards. However the testwas not waiting for the confirmation that the necessary records havebeen replayed on the standby, leading to spurious failures.Per buildfarm member loach. Thanks to Thomas Munro for the report andTom Lane for the failure analysis.Discussion:https://postgr.es/m/CA+hUKGLUpqG52xtriUz5RpmeKPoEfNxNc-CginG+Cx+X2-Ycew@mail.gmail.com
1 parentc015f85 commit364298b

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

‎src/test/recovery/t/016_min_consistency.pl

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,10 @@ BEGIN
9797
$primary->safe_psql('postgres','CHECKPOINT;');
9898
$primary->safe_psql('postgres','UPDATE test1 SET a = a + 1;');
9999

100+
# Wait for last record to have been replayed on the standby.
101+
$primary->wait_for_catchup($standby,'replay',
102+
$primary->lsn('insert'));
103+
100104
# Fill in the standby's shared buffers with the data filled in
101105
# previously.
102106
$standby->safe_psql('postgres','SELECT count(*) FROM test1;');

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp