Horton
Menu

Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade

Tomas Vondra <tomas.vondra@enterprisedb.com>

View thread
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Victor Yegorov <vyegorov@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Alexander Korotkov <aekorotkov@gmail.com>
Date: 2022-02-23T15:41:22Z
Lists: pgsql-bugs 
On 2/23/22 16:36, Tomas Vondra wrote:
>>
>> 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@postgresql.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?
> 

Sorry, I accidentally used Alexander's old address, so let me CC him
with the correct/current one.


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

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

  1. Fix default signature length for gist_ltree_ops

  2. Implement operator class parameters