Re: Move defaults toward ICU in 16?

Jeff Davis <pgsql@j-davis.com>

From: Jeff Davis <pgsql@j-davis.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2023-02-17T20:43:47Z
Lists: pgsql-hackers
On Fri, 2023-02-17 at 18:27 +0100, Pavel Stehule wrote:
> Today I tested icu for Czech sorting. It is a little bit slower, but
> not too much, but it produces partially different results.

Thank you for trying it.

If it's a significant slowdown, can you please send more information?
ICU version, libc version, and testcase?

> select row_number() over (order by nazev collate "cs-x-icu"), nazev
> from obce 
> except select row_number() over (order by nazev collate "cs_CZ"),
> nazev from obce;
> 
> returns a not empty set. So minimally for Czech collate, an index
> rebuild is necessary

Yes, that's true of any locale change, provider change, or even
provider version change.


-- 
Jeff Davis
PostgreSQL Contributor Team - AWS





Commits

  1. Build ICU support by default.

  2. Use ICU by default at initdb time.

  3. pg_upgrade: copy locale and encoding information to new cluster.