Horton
Menu

Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

Andres Freund <andres@anarazel.de>

View thread
From: Andres Freund <andres@anarazel.de>
To: Victor Yegorov <vyegorov@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Nikita Glukhov <n.gluhov@postgrespro.ru>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-07T01:32:02Z
Lists: pgsql-hackers 
Hi,

On 2022-03-07 01:12:07 +0200, Victor Yegorov wrote:
> пн, 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?..

No. That was what I was alluding to with "even if it wouldn't even help in
this case".

Greetings,

Andres Freund

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix default signature length for gist_ltree_ops

  2. Implement operator class parameters