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

Commit484a848

Browse files
committed
Fix pg_rewind regression failure after "fast promotion"
pg_rewind looks at the control file to determine the server's timeline. Ifthe standby performs a "fast promotion", the timeline ID in the controlfile is not updated until the next checkpoint. The startup process requestsa checkpoint immediately after promotion, so this is unlikely to be anissue in the real world, but the regression suite ran pg_rewind so quicklyafter promotion that the checkpoint had not yet completed.Reported by Stephen Frost
1 parent9d396af commit484a848

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

‎src/bin/pg_rewind/RewindTest.pm

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -242,6 +242,14 @@ sub promote_standby
242242
system_or_bail("pg_ctl -w -D$test_standby_datadir promote >>$log_path 2>&1");
243243
poll_query_until("SELECT NOT pg_is_in_recovery()",$connstr_standby)
244244
ordie"Timed out while waiting for promotion of standby";
245+
246+
# Force a checkpoint after the promotion. pg_rewind looks at the control
247+
# file todetermine what timeline the server is on, and that isn't updated
248+
# immediately at promotion, but only at the next checkpoint. When running
249+
# pg_rewind in remote mode, it's possible that we complete the test steps
250+
# after promotion so quickly that when pg_rewind runs, the standby has not
251+
# performed a checkpoint after promotion yet.
252+
standby_psql("checkpoint");
245253
}
246254

247255
subrun_pg_rewind

0 commit comments

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