Re: Remaining dependency on setlocale() - Mailing list pgsql-hackers

From Tristan Partin
Subject Re: Remaining dependency on setlocale()
Date
Msg-id D3BNOV3TA7KU.2LD03GA9Q4OZV@partin.io
Whole thread Raw
In response to Remaining dependency on setlocale()  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Remaining dependency on setlocale()
List pgsql-hackers
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-davis.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
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)



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: optimizing pg_upgrade's once-in-each-database steps
Next
From: Nathan Bossart
Date:
Subject: Re: is_superuser versus set_config_option's parallelism check