Re: add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached" - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached"
Date
Msg-id b16660809435d54845abc60d6c76bf1e6f6e1ba7.camel@j-davis.com
Whole thread Raw
In response to add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached"  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached"  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Wed, 2021-10-20 at 21:35 +0530, Bharath Rupireddy wrote:
> The  FATAL error "recovery ended before configured recovery target
> was
> reached" introduced by commit at [1] in PG 14 is causing the standby
> to go down after having spent a good amount of time in recovery.
> There
> can be cases where the arrival of required WAL (for reaching recovery
> target) from the archive location to the standby may take time and
> meanwhile the standby failing with the FATAL error isn't good.
> Instead, how about we make the standby wait for a certain amount of
> time (with a GUC) so that it can keep looking for the required WAL. 

How is archiving configured, and would it be possible to introduce
logic into the restore_command to handle slow-to-arrive WAL?

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Experimenting with hash tables inside pg_dump
Next
From: Masahiko Sawada
Date:
Subject: Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber