| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | 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:51:41 |
| Message-ID: | 682EB55D-631C-4256-9866-C3FD4CF6CD3C@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On February 24, 2022 5:44:57 PM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>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.
If we're breaking every ltree gist index, can we detect that it's not an index generated by the new version? Most people don'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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2022-02-25 01:56:04 | Re: Design of pg_stat_subscription_workers vs pgstats |
| Previous Message | Tom Lane | 2022-02-25 01:47:54 | Re: Proposal: Support custom authentication methods using hooks |