| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Subject: | Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade |
| Date: | 2022-02-23 15:36:32 |
| Message-ID: | c733dae0-15ba-bcdd-e465-1a9f2fdefebf@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>
> I got approval to send a table with its data and index in the subject
> datafile.
> Taken from the v14 database.
>
Thanks for the data! I've been able to reproduce the issue (load into
12, pg_upgrade to 14 and run the query). After bisecting this for a
while, this seems like a bug in PG13 commit
commit 911e70207703799605f5a0e8aad9f06cff067c63 (HEAD)
Author: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Date: Mon Mar 30 19:17:11 2020 +0300
Implement operator class parameters
...
It works fine when upgrading to an earlier build, and crashes since this
commit. I haven't investigated this further, but I guess there's some
thinko in gist_ltree_ops, affecting how we interpret existing indexes.
Alexander, any ideas?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2022-02-23 15:41:22 | Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade |
| Previous Message | Japin Li | 2022-02-23 13:54:49 | Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter |