Message-ID: <68c4928b1ad1fdda96511a4e22d9c8fbd9eb95e8.camel@j-davis.com>
Subject: Re: Remaining dependency on setlocale()
From: Jeff Davis <pgsql@j-davis.com>
To: Peter Eisentraut <peter@eisentraut.org>, Daniel Verite
	 <daniel@manitou-mail.org>
Cc: Thomas Munro <thomas.munro@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	pgsql-hackers@postgresql.org
Date: Wed, 12 Nov 2025 10:59:35 -0800
In-Reply-To: <215d5fa1-49c7-487c-a6be-e772c0b46805@eisentraut.org>
References: <5e709c7a-0504-426c-8a7d-e0701c334cd7@manitou-mail.org>
	 <215d5fa1-49c7-487c-a6be-e772c0b46805@eisentraut.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.3-0ubuntu1 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/68c4928b1ad1fdda96511a4e22d9c8fbd9eb95e8.camel%40j-davis.com>
Precedence: bulk

On Wed, 2025-11-12 at 19:41 +0100, Peter Eisentraut wrote:
> The impact area of LC_CTYPE is much larger and more complicated=20
> and possibly interacts with other settings and third-party libraries
> in=20
> ways that we don't understand yet and might not be able to change.=20
> That's why I'm more hesitant about it.

What do you think about making lc_ctype and/or lc_collate into GUCs
(like lc_messages), assuming we remove all known effects in the backend
first?

If we make the setting PGC_POSTMASTER, then it eliminates potential
problems with threading, because setlocale() would be called only once
before allowing connections. For platforms that support uselocale(), we
could allow it to be set more freely, for those who need it set to
different values in different backends.

It would also be easier to document, which would be nice. There could
be some confusion if various settings are inconsistent with each other,
but that's true currently. And we'd still enforce a ctype that's
consistent with the encoding, at least.

Regards,
	Jeff Davis