pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Victor Yegorov <vyegorov@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
Date: Wed, 23 Feb 2022 16:36:32 +0100
Message-ID: <c733dae0-15ba-bcdd-e465-1a9f2fdefebf@enterprisedb.com> (raw)
In-Reply-To: <CAGnEboiQ-cnhXceFa9WfXk7y06fuVVsf9WcmEdPerjqth8QJxA@mail.gmail.com>
References: <17406-71e02820ae79bb40@postgresql.org>
	<cb3a777a-99c7-f671-532d-b828a2223502@enterprisedb.com>
	<CAGnEbojzf-uObyWeu1MPNKaYsnL_U2kg48K6Ec43waPRBu3DrQ@mail.gmail.com>
	<788a0a51-b1e3-3601-5783-3f6488796ec4@enterprisedb.com>
	<CAGnEboiQ-cnhXceFa9WfXk7y06fuVVsf9WcmEdPerjqth8QJxA@mail.gmail.com>

>
> 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?


regards

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





view thread (15+ messages)  latest in thread

Message-ID: <c733dae0-15ba-bcdd-e465-1a9f2fdefebf@enterprisedb.com>
Permalink:  ../c733dae0-15ba-bcdd-e465-1a9f2fdefebf@enterprisedb.com/
Also on:    postgresql.org/message-id/c733dae0-15ba-bcdd-e465-1a9f2fdefebf@enterprisedb.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tomas.vondra@enterprisedb.com, vyegorov@gmail.com, pgsql-bugs@lists.postgresql.org, a.korotkov@postgrespro.ru
  Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
  In-Reply-To: <c733dae0-15ba-bcdd-e465-1a9f2fdefebf@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox