From: pinker <pinker@onet.eu>
To: pgsql-bugs@postgresql.org
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Date: Sun, 18 Oct 2020 13:03:34 -0700 (MST)
Message-ID: <1603051414438-0.post@n3.nabble.com> (raw)
In-Reply-To: <235509.1603051243@sss.pgh.pa.us>
References: <1603050466566-0.post@n3.nabble.com>
<1603050580276-0.post@n3.nabble.com>
<235509.1603051243@sss.pgh.pa.us>
Tom Lane-2 wrote
> pinker <
> pinker@
> > writes:
>> Do you need any futher details?
>
> Yes. The stack trace is interesting, but far from enough to solve
> the problem. Since it evidently is reproducible for you, maybe
> you could extract a self-contained test case?
>
> regards, tom lane
Hi Tom,
I'm absolutely ok to provide you with the all DDL but i'm not allow to
provide any data. Would that be ok with you?
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
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: pinker@onet.eu
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
In-Reply-To: <1603051414438-0.post@n3.nabble.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