Re: Custom Glibc collation version strings under LOCPATH - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Custom Glibc collation version strings under LOCPATH
Date
Msg-id dfd73a29-125b-4d8b-98b8-bcbf5f25b342@joeconway.com
Whole thread Raw
In response to Custom Glibc collation version strings under LOCPATH  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Custom Glibc collation version strings under LOCPATH
List pgsql-hackers
On 6/4/25 00:03, Thomas Munro wrote:
> One way to move to a newer glibc-based Linux distribution but keep the
> locales working the same* without keeping the associated zombie C code
> alive is to find the source system's collation definition source
> files, compile them with the localedef on the target system and point
> to the top-level directory with the environment variable LOCPATH.

I don't think this works in all cases because I have seen where sorting 
was affected by C code rather than than data changes.

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



pgsql-hackers by date:

Previous
From: * Neustradamus *
Date:
Subject: Re: Please update your contact list: It must be pgsql-hackers@lists.postgresql.org
Next
From: Oleg Tselebrovskiy
Date:
Subject: Cluster.pm psql() undefined $$stderr