Re: Custom Glibc collation version strings under LOCPATH

From: Joe Conway <mail(at)joeconway(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Custom Glibc collation version strings under LOCPATH
Date: 2025-06-04 13:52:57
Message-ID: dfd73a29-125b-4d8b-98b8-bcbf5f25b342@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Tselebrovskiy 2025-06-04 14:01:54 Cluster.pm psql() undefined $$stderr
Previous Message * Neustradamus * 2025-06-04 13:47:51 Re: Please update your contact list: It must be pgsql-hackers@lists.postgresql.org