From abb331da0a3454aebdb416fd19baf289063c254b Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Sat, 13 Dec 2025 16:56:07 +0100 Subject: [PATCH] Fix out-of-date comment on makeRangeConstructors We did define 4 functions in 4429f6a9e3, but in df73584431e7 we got rid of the 0- and 1-arg versions. Author: Paul A. Jungwirth Reviewed-by: Chao Li Discussion: https://www.postgresql.org/message-id/CA%2BrenyVQti3iC7LE4UxtQb4ROLYMs6%2Bu-d4LrN5U4idH1Ghx6Q%40mail.gmail.com --- src/backend/commands/typecmds.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/commands/typecmds.c b/src/backend/commands/typecmds.c index 0eb8e0a2bb0..be6ffd6ddb0 100644 --- a/src/backend/commands/typecmds.c +++ b/src/backend/commands/typecmds.c @@ -1767,7 +1767,7 @@ DefineRange(ParseState *pstate, CreateRangeStmt *stmt) * impossible to define a polymorphic constructor; we have to generate new * constructor functions explicitly for each range type. * - * We actually define 4 functions, with 0 through 3 arguments. This is just + * We actually define 2 functions, with 2 through 3 arguments. This is just * to offer more convenience for the user. */ static void -- 2.39.5