Re: Order changes in PG16 since ICU introduction - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Order changes in PG16 since ICU introduction
Date
Msg-id 05ad2b39-3d0f-e0aa-e0a3-086b998a26e8@enterprisedb.com
Whole thread Raw
In response to Re: Order changes in PG16 since ICU introduction  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Order changes in PG16 since ICU introduction
List pgsql-hackers
On 09.05.23 10:25, Alvaro Herrera wrote:
> 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.

Here is my proposed patch for this.

Attachment

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: de-catalog one error message
Next
From: Peter Eisentraut
Date:
Subject: Re: Order changes in PG16 since ICU introduction