Re: str_casefold: fix typo in error message

From: Steven Niu <niushiji(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: str_casefold: fix typo in error message
Date: 2026-01-13 02:16:29
Message-ID: MN2PR15MB302109CF64E84EA303D02A65A78EA@MN2PR15MB3021.namprd15.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Sent: Tuesday, January 13, 2026 10:09
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)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.Best regards,--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(), so I think the change should be:

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

thought?

Regards,
Steven

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2026-01-13 02:23:25 examine_variable ignored CollateExpr
Previous Message Chao Li 2026-01-13 02:14:02 Re: Use CASEFOLD() internally rather than LOWER()