RE: Order changes in PG16 since ICU introduction

From: "Regina Obe" <lr(at)pcorp(dot)us>
To: "'Jeff Davis'" <pgsql(at)j-davis(dot)com>, "'Robert Haas'" <robertmhaas(at)gmail(dot)com>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Peter Eisentraut'" <peter(dot)eisentraut(at)enterprisedb(dot)com>, "'Sandro Santilli'" <strk(at)kbt(dot)io>, <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: Order changes in PG16 since ICU introduction
Date: 2023-04-21 22:39:26
Message-ID: 000001d974a2$218d4290$64a7c7b0$@pcorp.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 refused to 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-04-21 22:55:22 Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands
Previous Message Melanie Plageman 2023-04-21 22:29:16 Move un-parenthesized syntax docs to "compatibility" for few SQL commands