From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Victor Yegorov <vyegorov@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
Date: Thu, 17 Feb 2022 17:35:00 +0100
Message-ID: <4eac5413-4267-d8e2-4d94-205d5256c498@enterprisedb.com> (raw)
In-Reply-To: <788a0a51-b1e3-3601-5783-3f6488796ec4@enterprisedb.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>
On 2/17/22 01:16, Tomas Vondra wrote:
> ...
>
>> How large is the table/index? Are you able to run the query with a
>> custom build (without values optimized out)? Any chance you still
>> have a
>> backup from before the pg_upgrade, on which you might run the query?
>>
>>
>> Yes, this is a test DB restored from backup in order to test out 14
>> upgrade, production is still running on 12.9.
>> v3_region is 2832 kB
>> region_ltree_path_idx_gist is 472 kB
>>
>
> That means it should be possible to reproduce the issue elsewhere by
> copying the files (and schema). Is there any sensitive data that'd
> prevent handing over this data?
>
Maybe we could also try just dumping the data (the ltree_path column),
so that we can load it into 12 cluster and do a binary upgrade. That
would be simpler than trying to copy the existing data files.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
In-Reply-To: <4eac5413-4267-d8e2-4d94-205d5256c498@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