From: Tom Lane <tgl@sss.pgh.pa.us>
To: kbarber@salesforce.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17337: Segmentation fault on updating row with ltree GIST index
Date: Tue, 14 Dec 2021 10:37:17 -0500
Message-ID: <259548.1639496237@sss.pgh.pa.us> (raw)
In-Reply-To: <17337-6264099dfbeb4705@postgresql.org>
References: <17337-6264099dfbeb4705@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> I've got a customer that was seeing a segfault whenever they were performing
> an update operation on a table after an upgrade from Postgres 10 to 13.5. I
> can't show all the data as this is private, but let me give you what details
> I have.
Any chance of creating a self-contained test case, perhaps with
synthetic data?
regards, tom lane
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: tgl@sss.pgh.pa.us, kbarber@salesforce.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17337: Segmentation fault on updating row with ltree GIST index
In-Reply-To: <259548.1639496237@sss.pgh.pa.us>
* 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