Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: Order changes in PG16 since ICU introduction
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Jeff Davis" <pgsql@j-davis.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 Regina Obe <lr@pcorp.us>,
 Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 Sandro Santilli <strk@kbt.io>,
 pgsql-hackers@lists.postgresql.org
In-Reply-To: <d321c19850a236e76850f00437a34b8f8f1abb90.camel@j-davis.com>
Date: Tue, 25 Apr 2023 17:00:19 +0200
Message-Id: <de4b36f0-a30b-4410-ba7b-e5f4c5915e6f@manitou-mail.org>
Archived-At: <https://www.postgresql.org/message-id/de4b36f0-a30b-4410-ba7b-e5f4c5915e6f%40manitou-mail.org>
Precedence: bulk

	Jeff Davis wrote:

> > (I'm not sure whether those operations can get redirected to ICU
> > today
> > or whether they still always go to libc, but we'll surely want to fix
> > it eventually if the latter is still true.)
>=20
> Those operations do get redirected to ICU today.=20

FTR the full text search parser still uses the libc functions
is[w]space/alpha/digit...  that depend on lc_ctype, whether the db
collation provider is ICU or not.


Best regards,
--=20
Daniel V=E9rit=E9
https://postgresql.verite.pro/
Twitter: @DanielVerite