Horton

Re: Move defaults toward ICU in 16?

Justin Pryzby <pryzby@telsasoft.com>

View thread View on postgr.es
From: Justin Pryzby <pryzby@telsasoft.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Jeff Davis <pgsql@j-davis.com>, Andres Freund <andres@anarazel.de>, Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2023-04-17T13:23:03Z
Lists: pgsql-hackers 
On Wed, Apr 05, 2023 at 09:33:25AM +0200, Peter Eisentraut wrote:
> On 16.03.23 14:52, Peter Eisentraut wrote:
> > On 09.03.23 20:14, Jeff Davis wrote:
> > > > Let's come back to that after dealing with the other two.
> > > 
> > > Leaving 0001 open for now.
> > 
> > I suspect making a change like this now would result in a bloodbath on
> > the build farm that we could do without.  I suggest revisiting this
> > after the commit fest ends.
> 
> I don't object to this patch.  I suggest waiting until next week to commit
> it and then see what happens.  It's easy to revert if it goes terribly.

Is this still being considered for v16 ?

-- 
Justin

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.