Re: Change initdb default to the builtin collation provider - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Change initdb default to the builtin collation provider
Date
Msg-id 3c015e118176ecd4b060e8343bf3b75f459ffcf5.camel@j-davis.com
Whole thread Raw
In response to Re: Change initdb default to the builtin collation provider  ("Daniel Verite" <daniel@manitou-mail.org>)
List 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




pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Change initdb default to the builtin collation provider
Next
From: Andres Freund
Date:
Subject: Re: Defend against -ffast-math in meson builds