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

From Jeff Davis
Subject Re: Move defaults toward ICU in 16?
Date
Msg-id d47923e2774cb5e5b6207f8678ffcc11bd110c4a.camel@j-davis.com
Whole thread Raw
In response to Re: Move defaults toward ICU in 16?  (Andres Freund <andres@anarazel.de>)
Responses Re: Move defaults toward ICU in 16?
List pgsql-hackers
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



Attachment

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Weird failure with latches in curculio on v15
Next
From: Andres Freund
Date:
Subject: Re: Move defaults toward ICU in 16?