| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: new environment variable INITDB_LOCALE_PROVIDER |
| Date: | 2025-10-14 20:45:00 |
| Message-ID: | ff5bd6a6d5968442e272e4cbcfc9d19f65ada38f.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2025-10-14 20:55:44 | Re: Improved TAP tests by replacing sub-optimal uses of ok() with better Test::More functions |
| Previous Message | Peter Eisentraut | 2025-10-14 19:51:01 | Re: new environment variable INITDB_LOCALE_PROVIDER |