On Thu, 2025-07-10 at 12:01 +1200, Thomas Munro wrote:
> I tried to make a portable PG_C_LOCALE mechanism like that, but it
> was
> reverted for reasons needing more investigation... see
> 8e993bff5326b00ced137c837fce7cd1e0ecae14 (reverted by
> 3c8e463b0d885e0d976f6a13a1fb78187b25c86f).
The revert seems to be related to pgport_shlib. At least for my current
work, I'm focused on removing setlocale() dependencies in the backend,
and a PG_C_LOCALE should work fine there.
Regards,
Jeff Davis
