On Wed, May 13, 2020 at 04:58:15AM +, 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 i
Thank you Kyotaro and Laurenz for your quick responses.
This helped me get my setup working.
Regards,
Mariya
On 13/05/20, 6:51 AM, "Kyotaro Horiguchi" wrote:
At Tue, 12 May 2020 17:29:50 +0200, Laurenz Albe
wrote in
> On Tue, 2020-05-12 at 09:40 +, Mariya Rampurawala wrote:
At Tue, 12 May 2020 17:29:50 +0200, Laurenz Albe
wrote in
> On Tue, 2020-05-12 at 09:40 +, Mariya Rampurawala wrote:
> > > but if the target cluster ran for a long time after the divergence,
> > > the old WAL files might no longer be present. In that case, they can
> > > be manually copied f
On Tue, 2020-05-12 at 09:40 +, Mariya Rampurawala wrote:
> > but if the target cluster ran for a long time after the divergence,
> > the old WAL files might no longer be present. In that case, they can
> > be manually copied from the WAL archive to the pg_wal directory, or
> > fetched on startu
Hi,
Thank you for the response.
> but if the target cluster ran for a long time after the divergence,
> the old WAL files might no longer be present. In that case, they can
> be manually copied from the WAL archive to the pg_wal directory, or
> fetched on startup by configuring pr
