public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Sandro Santilli <[email protected]>
To: Tom Lane <[email protected]>
Cc: Regina Obe <[email protected]>
Cc: [email protected]
Cc: Jeff Davis <[email protected]>
Subject: Re: Order changes in PG16 since ICU introduction
Date: Mon, 24 Apr 2023 17:10:04 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On 21.04.23 19:14, Peter Eisentraut wrote:
> On 21.04.23 19:09, Sandro Santilli wrote:
>> On Fri, Apr 21, 2023 at 11:48:51AM -0400, Tom Lane wrote:
>>> "Regina Obe" <[email protected]> writes:
>>>
>>>> https://trac.osgeo.org/postgis/ticket/5375
>>>
>>> If they actually are using locale C, I would say this is a bug.
>>> That should designate memcmp sorting and nothing else.
>>
>> Sounds like a bug to me. This is happening with a PostgreSQL cluster
>> created and served by a build of commit c04c6c5d6f :
>>
>> =# select version();
>> PostgreSQL 16devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
>> 11.3.0-1ubuntu1~22.04) 11.3.0, 64-bit
>> =# show lc_collate;
>> C
>> =# select '+' < '-';
>> f
>
> If the database is created with locale provider ICU, then lc_collate
> does not apply here, so the result might be correct (depending on what
> locale you have set).
The GUC settings lc_collate and lc_ctype are from a time when those
locale settings were cluster-global. When we made those locale settings
per-database (PG 8.4), we kept them as read-only. As of PG 15, you can
use ICU as the per-database locale provider, so what is being attempted
in the above example is already meaningless before PG 16, since you need
to look into pg_database to find out what is really happening.
I think we should just remove the GUC parameters lc_collate and lc_ctype.
view thread (45+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Order changes in PG16 since ICU introduction
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox