Horton

Re: Custom Glibc collation version strings under LOCPATH

Joe Conway <mail@joeconway.com>

View thread View on postgr.es
From: Joe Conway <mail@joeconway.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-06-05T01:00:26Z
Lists: pgsql-hackers 
On 6/4/25 19:35, Thomas Munro wrote:
> On Thu, Jun 5, 2025 at 3:44 AM Joe Conway <mail@joeconway.com> wrote:
>> If you go from anything pre-glibc-2.21 to post-glibc-2.21 I think you
>> will find that even with the same data files you get a different sort.
>> The same patch that caused the performance regression [1] (still present
>> in up to date glibc) also cause changes in sort order via C code alone.

> Finding more cases probably involves running something a little like
> Jeremy's torture tests across a huge gallery of versions and
> combinations of cross-version recompiled definitions.  Or something
> like that...

Sounds like great fun!

;-)

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com

Commits

  1. Use libc version as a collation version on glibc systems.