Re: Improve verification of recovery_target_timeline GUC.

[Michael Paquier]

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

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;
                }
        }

signature.asc
Description: PGP signature