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 Bharath Rupireddy
Subject Re: add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached"
Date
Msg-id CALj2ACX3qsz-JcekUsw06uQBCEZD7L0DKY02vk=Y7nyPd6W4fw@mail.gmail.com
Whole thread Raw
In response to Re: add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached"  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Sat, Oct 23, 2021 at 1:46 AM Jeff Davis <pgsql@j-davis.com> wrote:
> What do you want to do after the timeout happens? If you want to issue
> a WARNING instead of failing outright, perhaps that makes sense for
> exploratory PITR cases. That could be a simple boolean GUC without
> needing to introduce the timeout logic into the server.

Thanks Jeff. I posted the patch in a separate thread[1] for new GUC
(WARN + promotion or shutdown with FATAL error) in case the recovery
target isn't reached.

[1] -
https://www.postgresql.org/message-id/flat/CALj2ACWR4iaph7AWCr5-V9dXqpf2p5B%3D3fTyvLfL8VD_E%2Bx0tA%40mail.gmail.com.

Regards,
Bharath Rupireddy.



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Allow users to choose what happens when recovery target is not reached
Next
From: Ajin Cherian
Date:
Subject: Re: row filtering for logical replication