Re: pg_upgrade fails to preserve old versions of the predefined collations

28.11.2019 23:25, Thomas Munro пишет:
> On Fri, Nov 29, 2019 at 9:08 AM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
>> So for now it seems dangerous to use predefined collations as their old
>> versions are not preserved by pg_upgrade and the user doesn't know which
>> indexes affected by the actual ICU collation changes.
> Yeah, we noticed this while working on a proposal for new
> per-database-object version dependency tracking, and Peter E has
> written a patch to address it:
>
> https://commitfest.postgresql.org/25/2328/
Thank you! This patch is working for me. After pg_upgrade with the
applied patch I'm getting:
postgres=# SELECT oid, collname, collnamespace, collprovider,
collversion FROM pg_collation WHERE collname like 'ru%';
  oid  |  collname   | collnamespace | collprovider | collversion
-------+-------------+---------------+--------------+-------------
 17561 | ru-BY-x-icu |            11 | i            | 58.0.0.50
 17562 | ru-KG-x-icu |            11 | i            | 58.0.0.50
 17563 | ru-KZ-x-icu |            11 | i            | 58.0.0.50
 17564 | ru-MD-x-icu |            11 | i            | 58.0.0.50
 17565 | ru-RU-x-icu |            11 | i            | 58.0.0.50
 17566 | ru-UA-x-icu |            11 | i            | 58.0.0.50
 17567 | ru-x-icu    |            11 | i            | 58.0.0.50
 17568 | ru_RU       |            11 | c            |
 17569 | ru_RU.utf8  |            11 | c            |
 17696 | russian     |          2200 | i            | 58.0.0.50
(10 rows)

Best regards,
Alexander