Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Mariya Rampurawala <Mariya(dot)Rampurawala(at)veritas(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "laurenz(dot)albe(at)cybertec(dot)at" <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails
Date: 2020-05-13 07:25:55
Message-ID: 20200513072555.GN88791@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, May 13, 2020 at 04:58:15AM +0000, Mariya Rampurawala wrote:
> Thank you Kyotaro and Laurenz for your quick responses.
> This helped me get my setup working.

Please note that we have added in Postgres 13 the possibility to use a
restore_command when using pg_rewind if the parameter is set in the
target cluster's configuration. This way, you can fetch missing WAL
segments from archives during the rewind operation without the need to
rely on wal_keep_segments or such.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Amine Tengilimoglu 2020-05-13 07:34:35 Re: what is the best way to access cold data on another server?
Previous Message Holger Jakobs 2020-05-13 07:24:41 Re: what is the best way to access cold data on another server?