Re: new environment variable INITDB_LOCALE_PROVIDER - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: new environment variable INITDB_LOCALE_PROVIDER
Date
Msg-id ff5bd6a6d5968442e272e4cbcfc9d19f65ada38f.camel@j-davis.com
Whole thread Raw
In response to Re: new environment variable INITDB_LOCALE_PROVIDER  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Tue, 2025-10-14 at 21:51 +0200, Peter Eisentraut wrote:
> I'm skeptical that we want user-facing environment variables to
> provide
> initdb defaults.  The use for that hasn't really been explained.

One motivation was to make it smoother to change the initdb default
provider:

https://www.postgresql.org/message-id/9b259f4c532943e428e9665122f37c099bab250e.camel@j-davis.com
https://www.postgresql.org/message-id/e4ac16908dad3eddd3ed73c4862591375a3f0539.camel@j-davis.com

if we were to make that change, then users might have existing scripts
and want to use the environment variable to switch it back to libc
without modifying the scripts.

If you think we can change the initdb default without introducing an
environment variable, then perhaps we don't need v3-0002. What do you
think about v3-0001?

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: new environment variable INITDB_LOCALE_PROVIDER
Next
From: Andrew Dunstan
Date:
Subject: Re: Improved TAP tests by replacing sub-optimal uses of ok() with better Test::More functions