Re: EDB builds Postgres 13 with an obsolete ICU version

On Tue, Aug 18, 2020 at 09:44:35AM +0900, Michael Paquier wrote:
> On Mon, Aug 17, 2020 at 02:23:57PM -0400, Bruce Momjian wrote:
> > Also, is it the ICU library version we should be tracking for reindex,
> > or each _collation_ version? If the later, do we store the collation
> > version for each index?
>
> You need to store the collation version(s) for each index. This
> thread deals with the problem:
> https://commitfest.postgresql.org/29/2367/
> https://www.postgresql.org/message-id/CAEepm%3D0uEQCpfq_%2BLYFBdArCe4Ot98t1aR4eYiYTe%3DyavQygiQ%40mail.gmail.com
>
> That's not all of it as you would still need some filtering
> capabilities in the backend to reindex only the collation-sensitive
> indexes with a reindex, but that's one step forward into being able to
> do that.

Oh, we don't even have the version in the system catalogs yet? I guess
when pg_upgrade runs create_index we could grab it then, and for the
pg_upgrade _after_ that, do the checks. This seems like it is years
away from being useful.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee