| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Remaining dependency on setlocale() |
| Date: | 2024-08-06 21:59:55 |
| Message-ID: | 4c5da86af36a0d5e430eee3f60ce5e06f1b5cd34.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-08-06 22:15:57 | Re: Minor refactorings to eliminate some static buffers |
| Previous Message | Nathan Bossart | 2024-08-06 21:43:12 | Re: Remove dependence on integer wrapping |