Re: Order changes in PG16 since ICU introduction
От | Alvaro Herrera |
---|---|
Тема | Re: Order changes in PG16 since ICU introduction |
Дата | |
Msg-id | 20230509082553.yjikrxn54mi6hezc@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: Order changes in PG16 since ICU introduction (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Ответы |
Re: Order changes in PG16 since ICU introduction
Re: Order changes in PG16 since ICU introduction |
Список | pgsql-hackers |
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/
В списке pgsql-hackers по дате отправления: