Re: Move defaults toward ICU in 16?
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Andres Freund <andres@anarazel.de>
Cc: 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-14T17:48:08Z
Lists: pgsql-hackers
Attachments
- v3-0001-Build-ICU-support-by-default.patch (text/x-patch) patch v3-0001
- v3-0002-Use-ICU-by-default-at-initdb-time.patch (text/x-patch) patch v3-0002
On Fri, 2023-02-10 at 18:00 -0800, Andres Freund wrote: > Until something like my patch above is done more generally > applicable, I think > your patch should disable ICU on windows. Can't just fail to build. > > Perhaps we don't need to force ICU use to on with the meson build, > given that > it defaults to auto-detection? Done. I changed it back to 'auto', and tests pass. > > But, shouldn't pg_upgrade be able to deal with this? As long as the > databases > are created with template0, we can create the collations at that > point? Are you saying that the upgraded cluster could have a different default collation for the template databases than the original cluster? That would be wrong to do, at least by default, but I could see it being a useful option. Or maybe I misunderstand what you're saying? > > This stuff shouldn't be in here, it's due to a debian patched > autoconf. Removed, thank you. -- 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