Horton
Menu

Re: Improve verification of recovery_target_timeline GUC.

David Steele <david@pgbackrest.org>

View thread
From: David Steele <david@pgbackrest.org>
To: Michael Paquier <michael@paquier.xyz>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2025-07-04T13:39:00Z
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix constant in error message for recovery_target_timeline

  2. Improve checks for GUC recovery_target_timeline