Re: Move defaults toward ICU in 16? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Move defaults toward ICU in 16?
Date
Msg-id 20230214175957.idkb7shsqzp5nbll@awork3.anarazel.de
Whole thread Raw
In response to Re: Move defaults toward ICU in 16?  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Move defaults toward ICU in 16?
List pgsql-hackers
Hi,

On 2023-02-14 09:48:08 -0800, Jeff Davis wrote:
> On Fri, 2023-02-10 at 18:00 -0800, Andres Freund wrote:
> > 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?

I am saying that pg_upgrade should be able to deal with the difference. The
details of how to implement that, don't matter that much.

FWIW, I don't think it matters much what collation template0 has, since we
allow to change the locale provider when using template0 as the template.

We could easily update template0, if we think that's necessary. But I don't
think it really is. As long as the newly created databases have the right
provider, I'd lean towards not touching template0. But whatever...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Move defaults toward ICU in 16?
Next
From: Andres Freund
Date:
Subject: Re: Force testing of query jumbling code in TAP tests