Re: Order changes in PG16 since ICU introduction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Regina Obe" <lr(at)pcorp(dot)us>
Cc: "'Peter Eisentraut'" <peter(dot)eisentraut(at)enterprisedb(dot)com>, "'Sandro Santilli'" <strk(at)kbt(dot)io>, pgsql-hackers(at)lists(dot)postgresql(dot)org, "'Jeff Davis'" <pgsql(at)j-davis(dot)com>
Subject: Re: Order changes in PG16 since ICU introduction
Date: 2023-04-21 17:59:42
Message-ID: 3368986.1682099982@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Regina Obe" <lr(at)pcorp(dot)us> writes:
> Okay got it was on IRC with RhodiumToad and he suggested:
> CREATE DATABASE test2 TEMPLATE=template0 ENCODING = 'UTF8' LC_COLLATE = 'C'
> LC_CTYPE = 'C' ICU_LOCALE='C';

> Which gives expected result:
> SELECT '+' < '-' ; -- true

> but gives me a notice:
> NOTICE: using standard form "en-US-u-va-posix" for locale "C"

Yeah. My recommendation is just LOCALE:

regression=# CREATE DATABASE test1 TEMPLATE=template0 ENCODING = 'UTF8' LOCALE = 'C';
CREATE DATABASE
regression=# CREATE DATABASE test2 TEMPLATE=template0 ENCODING = 'UTF8' ICU_LOCALE = 'C';
NOTICE: using standard form "en-US-u-va-posix" for locale "C"
CREATE DATABASE

I think it's probably intentional that ICU_LOCALE is stricter
about being given a real ICU locale name, but I didn't write
any of that code.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2023-04-21 18:00:35 Re: Order changes in PG16 since ICU introduction
Previous Message Regina Obe 2023-04-21 17:56:14 RE: Order changes in PG16 since ICU introduction