Message-ID: <765286f264b138afdb11970bbaf57e7fdc4248eb.camel@j-davis.com>
Subject: Re: Order changes in PG16 since ICU introduction
From: Jeff Davis <pgsql@j-davis.com>
To: Regina Obe <lr@pcorp.us>, pgsql-hackers@lists.postgresql.org
Date: Fri, 21 Apr 2023 09:15:39 -0700
In-Reply-To: <000b01d97465$c34bbd60$49e33820$@pcorp.us>
References: <000b01d97465$c34bbd60$49e33820$@pcorp.us>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu1 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/765286f264b138afdb11970bbaf57e7fdc4248eb.camel%40j-davis.com>
Precedence: bulk

On Fri, 2023-04-21 at 11:27 -0400, Regina Obe wrote:
> A couple of days ago, our PostGIS PG16 bots started failing with
> order
> changes in text.
> We have our tests set to locale=3Dc

Are you sure it's still using the C locale? The results seem to be
explainable if the locale switched from "C" to "en-US-x-icu":

The results of the following are the same in v15 and v16:

select 'RM(25)/nodes|+|21|1' collate "C" < 'RM(25)/nodes|-|21|' collate
"C"; -- true

select 'RM(25)/nodes|+|21|1' collate "en-US-x-icu" < 'RM(25)/nodes|-
|21|' collate "en-US-x-icu"; -- false

I suspect when the initdb and configure defaults changed from libc to
ICU, then your locale changed.

Regards,
	Jeff Davis