Re: Move defaults toward ICU in 16?

Jeff Davis <pgsql@j-davis.com>

From: Jeff Davis <pgsql@j-davis.com>

To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, 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-20T19:41:52Z

Lists: pgsql-hackers

On Mon, 2023-02-20 at 15:55 +0100, Peter Eisentraut wrote:
> I'm confused.  We are not going to try to change existing databases
> to a 
> different collation provider during pg_upgrade, are we?

No, certainly not.

I interpreted Pavel's comments as a comparison of ICU and libc in
general and not specific to this patch. Changing providers obviously
requires an index rebuild to be safe.

-- 
Jeff Davis
PostgreSQL Contributor Team - AWS

Commits

Build ICU support by default.
- fcb21b3acdcb 16.0 landed
Use ICU by default at initdb time.
- 27b62377b47f 16.0 landed
pg_upgrade: copy locale and encoding information to new cluster.
- 9637badd9f92 16.0 landed