From: Michael Paquier <michael@paquier.xyz>
Date: Fri, 20 Feb 2026 07:17:57 +0000 (+0900)
Subject: Fix constant in error message for recovery_target_timeline
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0dc22fff64716dc3937705f0b7d0980475b164c1;p=thirdparty%2Fpostgresql.git

Fix constant in error message for recovery_target_timeline

The intention was to use PG_UINT32_MAX, not UINT_MAX.  Let's be
consistent and use the same constant.

Thinko in fd7d7b719137.

Author: David Steele <david@pgbackrest.org>
Discussion: https://postgr.es/m/aZfXO97jSQaTTlfD@paquier.xyz
---

diff --git a/src/backend/access/transam/xlogrecovery.c b/src/backend/access/transam/xlogrecovery.c
index c0c2744d45b..fc794693442 100644
--- a/src/backend/access/transam/xlogrecovery.c
+++ b/src/backend/access/transam/xlogrecovery.c
@@ -5070,7 +5070,7 @@ check_recovery_target_timeline(char **newval, void **extra, GucSource source)
 		if (timeline < 1 || timeline > PG_UINT32_MAX)
 		{
 			GUC_check_errdetail("\"%s\" must be between %u and %u.",
-								"recovery_target_timeline", 1, UINT_MAX);
+								"recovery_target_timeline", 1, PG_UINT32_MAX);
 			return false;
 		}
 	}