Re: str_casefold: fix typo in error message - Mailing list pgsql-hackers

From Steven Niu
Subject Re: str_casefold: fix typo in error message
Date
Msg-id MN2PR15MB302109CF64E84EA303D02A65A78EA@MN2PR15MB3021.namprd15.prod.outlook.com
Whole thread Raw
In response to str_casefold: fix typo in error message  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: str_casefold: fix typo in error message
List pgsql-hackers
From: Chao Li <li.evan.chao@gmail.com>
Sent: Tuesday, January 13, 2026 10:09
To: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Subject: str_casefold: fix typo in error message

Hi Hacker,Found this issue while reviewing the other patch. That looks like a copy-paste error from the initial
commit.Bestregards,--Chao Li (Evan)HighGo Software Co., Ltd.https://www.highgo.com/ 


Hi, Evan,

I have a comment. Since it is collid that's being checked and will be used by function pg_newlocale_from_collation(),
soI think the change should be: 

-                        "lower()"),
+                        "pg_newlocale_from_collation(()"),

thought?

Regards,
Steven


pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Use CASEFOLD() internally rather than LOWER()
Next
From: jian he
Date:
Subject: examine_variable ignored CollateExpr