Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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-02-25 01:44:57
Message-ID: 1737375.1645753497@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-02-25 01:47:54 Re: Proposal: Support custom authentication methods using hooks
Previous Message Kyotaro Horiguchi 2022-02-25 01:20:25 Re: Buffer Manager and Contention