Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
Дата
Msg-id 20220306223352.63k6matktg5evuax@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: ltree_gist indexes broken after pg_upgrade from 12 to 13  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: ltree_gist indexes broken after pg_upgrade from 12 to 13  (Victor Yegorov <vyegorov@gmail.com>)
Re: ltree_gist indexes broken after pg_upgrade from 12 to 13  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
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.

Greetings,

Andres Freund



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Smith
Дата:
Сообщение: Comment typo in CheckCmdReplicaIdentity
Следующее
От: Mark Dilger
Дата:
Сообщение: Re: Granting SET and ALTER SYSTE privileges for GUCs