Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jO0aF-00006n-DJ for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 15:01:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jO0aE-0007Jq-AZ for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 15:01:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jO0aE-0007Ji-4i for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 15:01:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jO0aB-0006ab-Is for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 15:01:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03DF11uU000395; Mon, 13 Apr 2020 11:01:01 -0400 From: Tom Lane To: Tomas Vondra cc: Kamil =?utf-8?B?Sm/FhGNh?= , pgsql-bugs@lists.postgresql.org Subject: Re: backend crash In-reply-to: <20200413114147.a42vf3tr3auybdtr@development> References: <87imi37spc.fsf@alfa.kjonca> <20200413114147.a42vf3tr3auybdtr@development> Comments: In-reply-to Tomas Vondra message dated "Mon, 13 Apr 2020 13:41:47 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <393.1586790061.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 13 Apr 2020 11:01:01 -0400 Message-ID: <394.1586790061@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tomas Vondra 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