On Sat, Aug 10, 2024 at 1:29 PM Thomas Munro <thomas.mu...@gmail.com> wrote: > Here is a new attempt at this can of portability worms.
Slightly better version: * it's OK to keep relying on the global locale in the backend; for now, we know that LC_NUMERIC is set in main(), and in the multi-threaded future calling setlocale() even transiently will be banned, so it seems it'll be OK to just keep doing that, right? * we could use LC_C_LOCALE to get a "C" locale slightly more efficiently on those; we could define it ourselves for other systems, using pg_get_c_locale()
v3-0001-Improve-locale-thread-safety-of-ECPG.patch
Description: Binary data
