| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Change initdb default to the builtin collation provider |
| Date: | 2026-03-11 17:43:54 |
| Message-ID: | 3c015e118176ecd4b060e8343bf3b75f459ffcf5.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2026-03-11 at 17:28 +0100, Daniel Verite wrote:
> Also, it's not obvious how initdb could choose an UTF-8 locale
> regardless of the environment.
Right.
> Personally I think that ignoring the environment's LC_* for the
> collations would be fine if we went for builtin/C.UTF-8 by default,
> as
> $subject suggests. But the level of enthusiasm for that from the
> community seems much lower than it would need to be for that kind of
> change to be acceptable.
At this point in the release cycle, it seems too late for $subject to
happen in 19. But I do find this discussion useful, so I hope we can
continue while it has some attention.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-03-11 17:48:31 | Re: Defend against -ffast-math in meson builds |
| Previous Message | Jeff Davis | 2026-03-11 17:39:30 | Re: Change initdb default to the builtin collation provider |