Re: Improve verification of recovery_target_timeline GUC.

From: David Steele <david(at)pgbackrest(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve verification of recovery_target_timeline GUC.
Date: 2025-07-04 13:39:00
Message-ID: cf04b7c6-7774-4ffb-86f5-ca85462d5fd6@pgbackrest.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/2/25 22:24, Michael Paquier wrote:
> On Fri, Apr 25, 2025 at 01:50:16PM +0000, David Steele wrote:
>> That was my expectation. I just had some time to get this patch updated so
>> took the opportunity.
>
> And well, now is the time to get this patch done. So, applied after
> an extra lookup, with a switch from UINT_MAX to PG_UINT32_MAX in the
> code.

Excellent, thank you! I'm also planning a similar improvement for
check_recovery_target_xid as we discussed up thread.

Regards,
-David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2025-07-04 14:12:12 Re: Using failover slots for PG-non_PG logical replication
Previous Message Daniel Gustafsson 2025-07-04 13:18:46 Re: Explicitly enable meson features in CI