| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Sandro Santilli <strk(at)kbt(dot)io>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Regina Obe <lr(at)pcorp(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Subject: | Re: Order changes in PG16 since ICU introduction |
| Date: | 2023-05-11 11:07:53 |
| Message-ID: | 05ad2b39-3d0f-e0aa-e0a3-086b998a26e8@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| 0001-Remove-read-only-server-settings-lc_collate-and-lc_c.patch | text/plain | 13.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-05-11 11:09:26 | Re: Order changes in PG16 since ICU introduction |
| Previous Message | Daniel Gustafsson | 2023-05-11 10:11:30 | Re: de-catalog one error message |