RE: Order changes in PG16 since ICU introduction

Поиск
Список
Период
Сортировка
От Regina Obe
Тема RE: Order changes in PG16 since ICU introduction
Дата
Msg-id 000001d974a2$218d4290$64a7c7b0$@pcorp.us
обсуждение исходный текст
Ответ на Re: Order changes in PG16 since ICU introduction  (Jeff Davis <pgsql@j-davis.com>)
Список pgsql-hackers
> > My opinion is that the switch to using ICU by default is ill-advised
> > and should be reverted.
>
> Most of the complaints seem to be complaints about v15 as well, and while
> those complaints may be a reason to not make ICU the default, they are also
> an argument that we should continue to learn and try to fix those issues
> because they exist in an already-released version.
> Leaving it the default for now will help us fix those issues rather than hide
> them.
>
> It's still early, so we have plenty of time to revert the initdb default if we need
> to.
>
> Regards,
>     Jeff Davis

I'm fine with that.  Sounds like it wouldn't be too hard to just pull it out at the end.

Before this, I didn't even know ICU existed in PG15. My first realization that ICU was even a thing was when my PG16
refusedto compile without adding my ICU path to my pkg-config or putting in --without-icu. 

So yah I suspect leaving it in a little bit longer will uncover some more issues and won't harm too much.

Thanks,
Regina




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Melanie Plageman
Дата:
Сообщение: Move un-parenthesized syntax docs to "compatibility" for few SQL commands
Следующее
От: Nathan Bossart
Дата:
Сообщение: Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands