From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Kamil Jońca <kjonca@fastmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: backend crash
Date: Mon, 13 Apr 2020 11:01:01 -0400
Message-ID: <394.1586790061@sss.pgh.pa.us> (raw)
In-Reply-To: <20200413114147.a42vf3tr3auybdtr@development>
References: <87imi37spc.fsf@alfa.kjonca>
<20200413114147.a42vf3tr3auybdtr@development>
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> On Mon, Apr 13, 2020 at 09:25:35AM +0200, Kamil Jońca wrote:
>> I have problem with (pseudo) random backend crashes.
>> They seems to happen at one query, but not every time.
> I've tried to reproduce this, but unfortunately it does not fail for me.
> Chances are this depends on data. Can you prepare a small data sample
> that would trigger the issue?
This is evidently a parallel-query worker, so it's unlikely you'd ever
get anywhere near this crash with a "small" data sample; for starters
there'd have to be enough data to prompt use of a parallel plan.
I doubt that the crash is very data-specific though. Maybe just fill
the table with a lot of dummy 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, tomas.vondra@2ndquadrant.com, kjonca@fastmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: backend crash
In-Reply-To: <394.1586790061@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