Feedback-ID: ia2694551:Fastmail
Date: Tue, 9 May 2023 10:25:53 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Sandro Santilli <strk@kbt.io>, Tom Lane <tgl@sss.pgh.pa.us>,
	Regina Obe <lr@pcorp.us>, pgsql-hackers@lists.postgresql.org,
	Jeff Davis <pgsql@j-davis.com>
Subject: Re: Order changes in PG16 since ICU introduction
Message-ID: <20230509082553.yjikrxn54mi6hezc@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <696054d1-bc88-b6ab-129a-18b8bce6a6f0@enterprisedb.com>
Archived-At: <https://www.postgresql.org/message-id/20230509082553.yjikrxn54mi6hezc%40alvherre.pgsql>
Precedence: bulk

On 2023-Apr-24, Peter Eisentraut wrote:

> The GUC settings lc_collate and lc_ctype are from a time when those locale
> settings were cluster-global.  When we made those locale settings
> per-database (PG 8.4), we kept them as read-only.  As of PG 15, you can use
> ICU as the per-database locale provider, so what is being attempted in the
> above example is already meaningless before PG 16, since you need to look
> into pg_database to find out what is really happening.
> 
> I think we should just remove the GUC parameters lc_collate and lc_ctype.

I agree with removing these in v16, since they are going to become more
meaningless and confusing.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/