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: Andrew Dunstan <andrew@dunslane.net>
Cc: 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-06T22:33:52Z
Lists: 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

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