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 1jO2AQ-000451-DU for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 16:42:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jO2AP-0003MD-2L for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 16:42:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jO2AO-0003M5-S9 for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 16:42:36 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jO2AM-0006Mk-7s for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 16:42:35 +0000 Received: by mail-wm1-x344.google.com with SMTP id r26so10643851wmh.0 for ; Mon, 13 Apr 2020 09:42:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=m1J5Ky/ZIGqhQeTWaa47PpfVMgqNTPEIf1Q3XxKMfAg=; b=buDjhGl7YF8cd4PkDz37y/XQ9RfN3fGRLUuxs5bqXyVihOpSxzacXoWcT4/B58nbvc I4jr4B9USqLoJc7mENetRpi7vsPG/Ce5EVCn+eWbCkovi4rVm/6FF2+VGj+zz1P28nTx 4YpfOcHO/2tTmlTwRCGz81V3BFkRbJDEJzWCjpkmHaLpphu5mMPxISW4T9/G/D8lj1Xr vV5W19g6E9T6w7n1rGrba42awXrENJ3n1nOL/P07iFVdP50lqGZqgPojiXtp6XfabCb2 yh2/HFaLdynuJNpN9lvDSoV8ZTj5chbS679EL6X9+teXuhE7i189365Py2z+DcypjFN0 49yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=m1J5Ky/ZIGqhQeTWaa47PpfVMgqNTPEIf1Q3XxKMfAg=; b=TXkH/KJZJJs4pw8H+jWhquHrWtmM342WHrD7sb0z3VTq+WDVFBxMXon4NG2eVj0DDR mJM+HeVCh1h1XzSQrdFF6OPKkTsHCXZbbShTmxIAZm+eBHVdYn7LhuJFdq1fnncc/Jzq eKvtlGxOkaRPUuYgvoC+lx1itAKiC/msUBjlENAD032Wgam6mjmYspE7a6pK+A/44F64 R4Oi2QkhlKV0+LfZbJ13ylFG8yMadDOstic1nJXILT/GzifKdSDqiGRBT8mP+PQsjDJL xTsTKWokndF4cviIJTKxMZGv7wdA2a5lWCZxySRKLs+SGLvkyLX+JAx1MZlwJzXeDdXs 8zHg== X-Gm-Message-State: AGi0PubG+0g5XmK1ynh0FLaLYsAkSKa4cKBoP/x7XRfOX9xQDHmLTg+X vhEg8ser/jvGtOLt+4xFCvD76Q== X-Google-Smtp-Source: APiQypKo5/N8KWORzdBNB5CET69xTL5HL1ONNwp/qF3YQs8oicDE3QfLawiestpH+VqniXueJI1alA== X-Received: by 2002:a7b:cb59:: with SMTP id v25mr19556872wmj.139.1586796152635; Mon, 13 Apr 2020 09:42:32 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id r17sm6016884wrn.43.2020.04.13.09.42.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Apr 2020 09:42:32 -0700 (PDT) Date: Mon, 13 Apr 2020 18:42:30 +0200 From: Tomas Vondra To: Kamil =?utf-8?B?Sm/FhGNh?= Cc: Tom Lane , pgsql-bugs@lists.postgresql.org Subject: Re: backend crash Message-ID: <20200413164230.lvlfbippew7ulzsh@development> References: <87imi37spc.fsf@alfa.kjonca> <20200413114147.a42vf3tr3auybdtr@development> <394.1586790061@sss.pgh.pa.us> <20200413153246.r5amtd62cxvwlqkn@development> <87o8rv5q79.fsf@alfa.kjonca> <20200413161913.2oytbclavuwi3fnx@development> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200413161913.2oytbclavuwi3fnx@development> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Apr 13, 2020 at 06:19:13PM +0200, Tomas Vondra wrote: >On Mon, Apr 13, 2020 at 06:02:34PM +0200, Kamil Jońca wrote: >>Tomas Vondra writes: >> >>>On Mon, Apr 13, 2020 at 11:01:01AM -0400, Tom Lane wrote: >>>>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? >>>> >>> >>>I did that, of course, and the plan looks like this: >>> >> >>1. Did you try run this many times? As I wrote this does not crash every >>time. I can reproduce this on my data by running query 1000 times in >>loop. > >I did run it about 100x, I'll reduce the amount of data and let it run. > >How often it crashes? What execution plan does it use? > Also, presumably you're building from source, right? What configure options are you using? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services