Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Tomas Vondra <tomas.vondra@enterprisedb.com>

Cc: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2022-02-25T01:44:57Z

Lists: pgsql-hackers

Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
> I wonder if we could check the index tuple length, and adjust the siglen
> based on that, somehow ...

In an already-corrupted index, there won't be a unique answer.

			regards, tom lane

Commits

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

Fix default signature length for gist_ltree_ops
- bad202c615c9 13.7 landed
- 7d30f59da714 14.3 landed
- 7e74aafc4335 15.0 landed
Implement operator class parameters
- 911e70207703 13.0 cited