From: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix pg_rewind regression failure after "fast promotion" |
Date: | 2015-05-01 05:07:04 |
Message-ID: | E1Yo3AG-0006yD-QU@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/484a848a73fc5a76c16bc73626b290154b6a57b4
Modified Files
--------------
src/bin/pg_rewind/RewindTest.pm | 8 ++++++++
1 file changed, 8 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-05-01 09:55:08 | pgsql: Fix unaligned memory access in xlog parsing due to replication o |
Previous Message | Peter Eisentraut | 2015-05-01 04:03:14 | Re: shared_libperl, shared_libpython |