Re: ltree_gist indexes broken after pg_upgrade from 12 to 13 - Mailing list pgsql-hackers

From Victor Yegorov
Subject Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
Date
Msg-id CAGnEbohZ-Qp_C4K05Wpt7Gbe_KjWV3EUugci=53PcaWpPf3BwQ@mail.gmail.com
Whole thread Raw
In response to Re: ltree_gist indexes broken after pg_upgrade from 12 to 13  (Andres Freund <andres@anarazel.de>)
Responses Re: ltree_gist indexes broken after pg_upgrade from 12 to 13  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
пн, 7 мар. 2022 г. в 00:34, Andres Freund <andres@anarazel.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

pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: Granting SET and ALTER SYSTE privileges for GUCs
Next
From: Peter Smith
Date:
Subject: Re: Optionally automatically disable logical replication subscriptions on error