pgsql: Fix single-record reads to use restore_command if available in p

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix single-record reads to use restore_command if available in p
Date: 2020-04-21 23:09:01
Message-ID: E1jR20j-0001iJ-L1@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/cd123234404ef9a45415060633d3be31329820b2

Modified Files
--------------
src/bin/pg_rewind/parsexlog.c | 4 +++-
src/bin/pg_rewind/pg_rewind.c | 3 ++-
src/bin/pg_rewind/pg_rewind.h | 2 +-
3 files changed, 6 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2020-04-21 23:31:57 Re: Add "-Wimplicit-fallthrough" to default flags (was Re: pgsql: Support FETCH FIRST WITH TIES)
Previous Message Alvaro Herrera 2020-04-21 22:38:15 pgsql: psql \d: Display table where trigger is defined, if inherited