Re: Improve verification of recovery_target_timeline GUC.

Michael Paquier <michael@paquier.xyz>

View thread

From: Michael Paquier <michael@paquier.xyz>

To: David Steele <david@pgbackrest.org>

Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-02-20T03:38:35Z

Lists: pgsql-hackers

Attachments

uint32.patch (text/plain) patch

On Fri, Feb 20, 2026 at 03:25:30AM +0000, David Steele wrote:
> I noticed that when you replaced UINT_MAX with PG_UINT32_MAX you missed one
> instance. Fixed in the attached.

Added pgsql-hackers in CC for awareness, with your proposed patch
attached, David.

It looks so.  Will fix, thanks!
--
Michael

Commits

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

Fix constant in error message for recovery_target_timeline
- 0dc22fff6471 19 (unreleased) landed
Improve checks for GUC recovery_target_timeline
- fd7d7b719137 19 (unreleased) landed