From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Jeff Davis <pgsql@j-davis.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Sandro Santilli <strk@kbt.io>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Regina Obe <lr@pcorp.us>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Order changes in PG16 since ICU introduction
Date: Thu, 11 May 2023 13:09:26 +0200
Message-ID: <ec13488f-281d-cd15-3c11-afe080f98212@enterprisedb.com> (raw)
In-Reply-To: <3a00d1f05299d381dc701d283f95d845c741c6a1.camel@j-davis.com>
References: <20230509082553.yjikrxn54mi6hezc@alvherre.pgsql>
<3a00d1f05299d381dc701d283f95d845c741c6a1.camel@j-davis.com>
On 09.05.23 17:09, Jeff Davis wrote:
> It's awkward for a user to read pg_database.datlocprovider, then
> depending on that, either look in datcollate or daticulocale. (It's
> awkward in the code, too.)
>
> Maybe some built-in function that returns a tuple of the default
> provider, the locale, and the version? Or should we also output the
> ctype somehow (which affects the results of upper()/lower())?
There is also the deterministic flag and the icurules setting.
Depending on what level of detail you imagine the user needs, you really
do need to look at the whole picture, not some subset of it.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, pgsql@j-davis.com, alvherre@alvh.no-ip.org, strk@kbt.io, tgl@sss.pgh.pa.us, lr@pcorp.us, pgsql-hackers@lists.postgresql.org
Subject: Re: Order changes in PG16 since ICU introduction
In-Reply-To: <ec13488f-281d-cd15-3c11-afe080f98212@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox