Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
От | Andrew Dunstan |
---|---|
Тема | Re: ltree_gist indexes broken after pg_upgrade from 12 to 13 |
Дата | |
Msg-id | ba6da883-ad96-6701-23c0-e6b7c8b7dfc5@dunslane.net обсуждение исходный текст |
Ответ на | Re: ltree_gist indexes broken after pg_upgrade from 12 to 13 (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
Re: ltree_gist indexes broken after pg_upgrade from 12 to 13 |
Список | pgsql-hackers |
On 3/6/22 17:33, Andres Freund wrote: > Hi, > > On 2022-03-06 07:46:04 -0500, Andrew Dunstan wrote: >> This is an area not currently touched by the buildfarm's cross version >> upgrade testing, which basically compares a pre-upgrade and post-upgrade >> dump of the databases. The upgraded cluster does contain >> contrib_regression_ltree. >> >> I'm open to suggestions on how we might improve the buildfarm's testing >> of upgraded indexes generally. > 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. > See <https://github.com/PGBuildFarm/client-code/commit/191df23bd25eb5546b0989d71ae92747151f9f39> This will be in the next release cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: