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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade fails to preserve old versions of the predefined collations
Date: 2019-11-28 20:25:02
Message-ID: CA+hUKG+6MWf4DKq6KGDOe4xOnOAu9KDH_7CDonKvjvKOZtdz9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2019-11-28 20:58:02 Re: pg_upgrade fails to preserve old versions of the predefined collations
Previous Message Alexander Lakhin 2019-11-28 20:08:08 pg_upgrade fails to preserve old versions of the predefined collations