Fix single-record reads to use restore_command if available in pg_rewind
authorMichael Paquier <michael@paquier.xyz>
Tue, 21 Apr 2020 23:08:28 +0000 (08:08 +0900)
committerMichael Paquier <michael@paquier.xyz>
Tue, 21 Apr 2020 23:08:28 +0000 (08:08 +0900)
commitcd123234404ef9a45415060633d3be31329820b2
tree86be45c66105a0341bda751617c48e031a585f73
parentc33869cc3bfc42bce822251f2fa1a2a346f86cc5
Fix single-record reads to use restore_command if available in pg_rewind

readOneRecord() is used now when looking for a checkpoint record to
check if the target server is an ancestor of the source across multiple
timelines, and using a restore_command if available improves the
stability of the operation.  This part was missed in a7e8ece.

Reported-by: Kyotaro Horiguchi
Discussion: https://postgr.es/m/20200421.150830.1410714948345179794.horikyota.ntt@gmail.com
src/bin/pg_rewind/parsexlog.c
src/bin/pg_rewind/pg_rewind.c
src/bin/pg_rewind/pg_rewind.h