diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2015-04-30 21:57:18 -0700 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2015-04-30 21:59:58 -0700 |
| commit | 484a848a73fc5a76c16bc73626b290154b6a57b4 (patch) | |
| tree | 11a9ef6c962d9e8d4b204142f58f348900f2e809 /src/backend/executor/nodeCustom.c | |
| parent | 9d396af46357df1243aff4a9ca4f4987e4fe6024 (diff) | |
| download | postgresql-484a848a73fc5a76c16bc73626b290154b6a57b4.tar.gz postgresql-484a848a73fc5a76c16bc73626b290154b6a57b4.zip | |
Fix pg_rewind regression failure after "fast promotion"
pg_rewind looks at the control file to determine the server's timeline. If
the standby performs a "fast promotion", the timeline ID in the control
file is not updated until the next checkpoint. The startup process requests
a checkpoint immediately after promotion, so this is unlikely to be an
issue in the real world, but the regression suite ran pg_rewind so quickly
after promotion that the checkpoint had not yet completed.
Reported by Stephen Frost
Diffstat (limited to 'src/backend/executor/nodeCustom.c')
0 files changed, 0 insertions, 0 deletions