| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | 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-10 17:24:19 |
| Message-ID: | 20220310172419.ik6gt5fylhvinl74@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-03-10 10:43:06 -0500, Andrew Dunstan wrote:
> On 3/6/22 17:33, Andres Freund wrote:
> > 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
Great, thanks for doing that!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-03-10 17:26:08 | Re: role self-revocation |
| Previous Message | Tom Lane | 2022-03-10 17:11:59 | Re: pg_stat_statements and "IN" conditions |