Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

From: Victor Yegorov <vyegorov(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
Date: 2022-03-06 23:12:07
Message-ID: CAGnEbohZ-Qp_C4K05Wpt7Gbe_KjWV3EUugci=53PcaWpPf3BwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

пн, 7 мар. 2022 г. в 00:34, Andres Freund <andres(at)anarazel(dot)de>:

> One thing that's likely worth doing as part of the cross version upgrade
> test,
> even if it wouldn't even help in this case, is to run amcheck post
> upgrade. Just dumping data isn't going to touch indices at all.
>
> A sequence of
> pg_upgrade; amcheck; upgrade all extensions; amcheck;
> would make sense.
>

Is it possible to amcheck gist indexes?..

--
Victor Yegorov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2022-03-06 23:25:21 Re: Optionally automatically disable logical replication subscriptions on error
Previous Message Mark Dilger 2022-03-06 23:06:43 Re: Granting SET and ALTER SYSTE privileges for GUCs