Hi,
On February 24, 2022 5:44:57 PM PST, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>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.
If we're breaking every ltree gist index, can we detect that it's not an index generated by the new version? Most
peopledon't read release notes, and this is just about guaranteed to break all.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
