| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tristan Partin <tristan(at)neon(dot)tech>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On non-Windows, hard depend on uselocale(3) |
| Date: | 2024-08-10 03:48:45 |
| Message-ID: | CA+hUKGLs9ccA7pUfphZOuf_fcVq2FAai7Cm0pmbQk0Qcs4VoVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Aug 10, 2024 at 1:29 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)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()
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Improve-locale-thread-safety-of-ECPG.patch | application/octet-stream | 30.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2024-08-10 03:52:23 | Re: On non-Windows, hard depend on uselocale(3) |
| Previous Message | Thomas Munro | 2024-08-10 01:36:39 | Re: Remaining dependency on setlocale() |