Feedback-ID: idd01497b:Fastmail
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8; format=Flowed
Date: Fri, 09 Aug 2024 15:16:58 -0500
Message-Id: <D3BNOV3TA7KU.2LD03GA9Q4OZV@partin.io>
Cc: "pgsql-hackers" <pgsql-hackers@postgresql.org>
Subject: Re: Remaining dependency on setlocale()
To: "Jeff Davis" <pgsql@j-davis.com>
From: "Tristan Partin" <tristan@partin.io>
References: <4c5da86af36a0d5e430eee3f60ce5e06f1b5cd34.camel@j-davis.com>
In-Reply-To: <4c5da86af36a0d5e430eee3f60ce5e06f1b5cd34.camel@j-davis.com>
Archived-At: 
 <https://www.postgresql.org/message-id/D3BNOV3TA7KU.2LD03GA9Q4OZV%40partin.io>
Precedence: bulk

On Tue Aug 6, 2024 at 5:00 PM CDT, Jeff Davis wrote:
> After some previous work here:
>
> https://postgr.es/m/89475ee5487d795124f4e25118ea8f1853edb8cb.camel@j-davi=
s.com
>
> we are less dependent on setlocale(), but it's still not completely
> gone.
>
> setlocale() counts as thread-unsafe, so it would be nice to eliminate
> it completely.
>
> The obvious answer is uselocale(), which sets the locale only for the
> calling thread, and takes precedence over whatever is set with
> setlocale().
>
> But there are a couple problems:
>
> 1. I don't think it's supported on Windows.
>
> 2. I don't see a good way to canonicalize a locale name, like in
> check_locale(), which uses the result of setlocale().
>
> Thoughts?

Hey Jeff,

See this thread[0] for some work that I had previously done. Feel free=20
to take it over, or we could collaborate.

[0]: https://www.postgresql.org/message-id/CWMW5OZBWJ10.1YFLQWSUE5RE9@neon.=
tech

--
Tristan Partin
Neon (https://neon.tech)