Re: Custom Glibc collation version strings under LOCPATH

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Custom Glibc collation version strings under LOCPATH
Date: 2025-06-04 10:39:41
Message-ID: CA+hUKGLuCeA+R04kH7QVHL2EKv8adAhxAd7aH7ZKLmEtS_-3gw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 4, 2025 at 9:17 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> I wonder why you want to capture LOCPATH early in main.c. It seems
> sufficient to look it up when needed?

Right, it is setenv() that we're trying to avoid. Updated.

Attachment Content-Type Size
v2-0001-Load-optional-collation-version-from-glibc-LOCPAT.patch text/x-patch 6.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alena Rybakina 2025-06-04 10:40:07 Re: pull-up subquery if JOIN-ON contains refs to upper-query
Previous Message Fabrice Chapuis 2025-06-04 10:30:48 synchronized_standby_slots used in logical replication