Re: EDB builds Postgres 13 with an obsolete ICU version - Mailing list pgsql-hackers

From Dave Page
Subject Re: EDB builds Postgres 13 with an obsolete ICU version
Date
Msg-id CA+OCxoyfVjz9VTGn-9xFCQ3CYD=cynGEWOkn+fptPz_pshvYWA@mail.gmail.com
Whole thread Raw
In response to Re: EDB builds Postgres 13 with an obsolete ICU version  (Bruce Momjian <bruce@momjian.us>)
Responses Re: EDB builds Postgres 13 with an obsolete ICU version  (Thomas Kellerer <shammat@gmx.net>)
Re: EDB builds Postgres 13 with an obsolete ICU version  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers


On Tue, Aug 4, 2020 at 1:04 AM Bruce Momjian <bruce@momjian.us> wrote:
On Mon, Aug  3, 2020 at 08:56:06PM +0200, Daniel Verite wrote:
>  Hi,
>
> As a follow-up to bug #16570 [1] and other previous discussions
> on the mailing-lists, I'm checking out PG13 beta for Windows
> from:
https://www.enterprisedb.com/postgresql-early-experience
> and it ships with the same obsolete ICU 53 that was used
> for PG 10,11,12.
> Besides not having the latest Unicode features and fixes, ICU 53
> ignores the BCP 47 tags syntax in collations used as examples
> in Postgres documentation, which leads to confusion and
> false bug reports.
> The current version is ICU 67.
>
> I don't see where the suggestion to upgrade it before the
> next PG release should be addressed but maybe some people on
> this list do know or have the leverage to make it happen?

Well, you can ask EDB about this, but perhaps the have kept the same ICU
version so indexes will not need to be reindexed.

Correct - updating ICU would mean a reindex is required following any upgrade, major or minor.

I would really like to find an acceptable solution to this however as it really would be good to be able to update ICU.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH v1] elog.c: Remove special case which avoided %*s format strings..
Next
From: Konstantin Knizhnik
Date:
Subject: LSM tree for Postgres