Re: On non-Windows, hard depend on uselocale(3)
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>,
Michael Paquier <michael@paquier.xyz>, Andrew Dunstan <andrew@dunslane.net>,
Tristan Partin <tristan@neon.tech>, Tom Lane <tgl@sss.pgh.pa.us>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-28T16:32:47Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Revert "Tidy up locale thread safety in ECPG library."
- 3c8e463b0d88 18.0 landed
-
Tidy up locale thread safety in ECPG library.
- 8e993bff5326 18.0 landed
-
Revert "Blind attempt to fix _configthreadlocale() failures on MinGW."
- a62d90f2e5cb 18.0 landed
-
Require ucrt if using MinGW.
- 1758d4244616 18.0 landed
-
Remove configure check for _configthreadlocale().
- f1da075d9a03 18.0 landed
-
Simplify checking for xlocale.h
- 9c2a6c5a5f4b 18.0 landed
-
All supported systems have locale_t.
- 8d9a9f034e92 17.0 cited
On 28.03.25 17:14, Masahiko Sawada wrote: > On Fri, Mar 28, 2025 at 8:30 AM Peter Eisentraut <peter@eisentraut.org> wrote: >> >> On 09.02.25 08:32, Peter Eisentraut wrote: >>> Checking the status of this thread ... >>> >>> The patches that removed the configure checks for _configthreadlocale(), >>> and related cleanup, have been committed. >>> >>> The original patch to "Tidy up locale thread safety in ECPG library" is >>> still outstanding. >>> >>> Attached is a rebased version, based on the posted v6, with a couple of >>> small fixups from me. >>> >>> I haven't re-reviewed it yet, but from scanning the discussion, it looks >>> close to done. >> >> After staring at this a few more times, I figured it was ready enough >> and I committed it. > > It seems that some bf animals such as jackdaw are unhappy with this > commit[0][1]. I also got the same 'undefined reference to symbol > error' locally when building test_json_parser. Yeah, looks like we'll have to revert this for now. But I'm confused, because I don't see any clear pattern for which platforms or configurations it's failing and for which not.