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 1jO1nu-0003Bz-7E for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 16:19:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jO1nt-0003Na-4t for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 16:19:21 +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 1jO1ns-0003Jd-Q9 for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 16:19:20 +0000 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jO1nq-0006Ct-5Y for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 16:19:19 +0000 Received: by mail-wm1-x342.google.com with SMTP id a201so10170456wme.1 for ; Mon, 13 Apr 2020 09:19:17 -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=cAdhfKiWYMwpVBs19MX0XQGhwU61XuuKKXd/jKidsUQ=; b=XzvRrZuFg3VyUS6S048TkcmLFJGU1kYream6DFn7KvAUI6CNXQX8u8SF9RCpC07Ebm UaqhE6FXfZysVNQibMqvcY7GRKYm8fRMkQmJTAvdbZ6P5TpgH2Lan5C66DWRX/uaYNz4 KNZUfF1LPHmmj2jp4glX3frbrhpqpf1osQ5s3qYq61ZcYECQM13PYmmGeamPMro4cY2T ixghBSfjnA8hr8m8/xObDLH0FM06TQSXZmGx0TZnnW+UF8Y5xKlSGuRfhXaRSVUDw33w EpYbbwx4vJmTMJWnUDga7pX33DU6GmYlwVPn/RcefA+vMe5V3754hK6sjkWHzUTkVG2G FLOw== 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=cAdhfKiWYMwpVBs19MX0XQGhwU61XuuKKXd/jKidsUQ=; b=g4tU6gYdx4ZWrq0bSDwWN1T4hVoGSA882C1guM2Oe60f9ywrZPgirIflIyrHVCQz1E 7XPk7E4jqAR3+Eg8VMBgDd+S+JiI8XywCRiiHtasgePOpaaRJQWUyd3p5tmA8XIe7XVI 5mKhtJ8mI3YUtGEZgQAMWnQ4OIR+wHrkMiCBKCyHdZcJKHpTy0RCrQSNKfZUxbxUgZJX WROcC9fURnS9dLdldBcA708rvv7NGl4Y7eIPz+Tfh0R1MsvZIXpPDAv0ghUO/H0janGV 3GSEA8le1pf2gTuEK+zbyKGHlHdlM7oJnPuSkc0FryvN7RYpHv8kzHroets7dVgxMCdY /5+A== X-Gm-Message-State: AGi0PuYYOid8dXzyIKMki8ELrBJoArwtM0zdkBqwWTyBess7LYxCkH8o ypOI/eGiKc0Qpeg686tXwz2C2Q== X-Google-Smtp-Source: APiQypIY9V5zeBpwVYs8w5r3+gEefbwZ3O6jSZZUFqd2hLFPGZ31i5W5A/4v0YTEAMJEZhBwJ7P69A== X-Received: by 2002:a05:600c:21d6:: with SMTP id x22mr20275944wmj.95.1586794755786; Mon, 13 Apr 2020 09:19:15 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id b85sm15607234wmb.21.2020.04.13.09.19.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Apr 2020 09:19:15 -0700 (PDT) Date: Mon, 13 Apr 2020 18:19:13 +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: <20200413161913.2oytbclavuwi3fnx@development> References: <87imi37spc.fsf@alfa.kjonca> <20200413114147.a42vf3tr3auybdtr@development> <394.1586790061@sss.pgh.pa.us> <20200413153246.r5amtd62cxvwlqkn@development> <87o8rv5q79.fsf@alfa.kjonca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87o8rv5q79.fsf@alfa.kjonca> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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? >2. I can try to prepare test data, but it will be rather long >process. Stay tuned :/ OK -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services