| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
| 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-07 01:32:02 |
| Message-ID: | 20220307013202.3vldnfbftn4bqzpv@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-03-07 01:12:07 +0200, Victor Yegorov wrote:
> пн, 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?..
No. That was what I was alluding to with "even if it wouldn't even help in
this case".
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-03-07 01:36:24 | Re: Comment typo in CheckCmdReplicaIdentity |
| Previous Message | Andres Freund | 2022-03-07 01:30:15 | Re: Time to drop plpython2? |