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:46:25
Message-ID: 3367226.1682099185@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:
> On my mingw64 setup, I built a test database on PG16 (built with icu
> support) and PG15 (no icu support)

> CREATE DATABASE test TEMPLATE=template0 ENCODING = 'UTF8' LC_COLLATE = 'C'
> LC_CTYPE = 'C';

As has been pointed out already, setting LC_COLLATE/LC_CTYPE is
meaningless when the locale provider is ICU. You need to look
at what ICU locale is being chosen, or force it with LOCALE = 'C'.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Regina Obe 2023-04-21 17:56:14 RE: Order changes in PG16 since ICU introduction
Previous Message Tom Lane 2023-04-21 17:41:08 Re: Commitfest 2023-03 starting tomorrow!