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 1jO14z-0001U3-MQ for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 15:32:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jO14x-0006uu-J9 for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Apr 2020 15:32:55 +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 1jO14x-0006r1-Cq for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 15:32:55 +0000 Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jO14s-0005rx-Gs for pgsql-bugs@lists.postgresql.org; Mon, 13 Apr 2020 15:32:53 +0000 Received: by mail-wm1-x343.google.com with SMTP id h2so9678575wmb.4 for ; Mon, 13 Apr 2020 08:32:50 -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=0QTu6tRUDZsQy2KPOuO7pmrwDNXw6sD63paHJOxcFNY=; b=1NrBabxU9+8NIayNHHuV8Xp4QN6GulMPC3fhRS/e+SY8G7iQwsPnzl+ABk2qS+welz aOXlmX31QIf9gorPt7a/5WDJSGf/HwlpRwiRY28AaoqkSEFLM8aX/p5XYTMSUAGJuwOE dnWkkGCLb+ag5gw7E5eG5J70ssnP7CkvjQTJsH3ipauI6fubStaIQES/z71M4XopTlmA +NsfHyy1teqMxxU7PRhp8AFfkX2ot73uULLzCuqdwCvZh/b6ezF2RNjgtm85P15Q80p9 gYo5osd1SRqLVw7t0272yBmx/lCaD+q1Ic7zlkHSYETYKgPi/VkeqjHwb8YulgsmJ4Gl +zuw== 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=0QTu6tRUDZsQy2KPOuO7pmrwDNXw6sD63paHJOxcFNY=; b=fHFOWTcudctnFtovaVMOttswqg8rT/ztLrrsCv0zAAVkizkHQIvofPoDNc3LCln6iD /RQXOk2CQu2179SlGkslqVC76utnacII9UCzIvyFTlUk0+8aFeu4NRRKUNAS/s0oMO3g crd+faMEfdtEMXFxeU39eVpyRywntdGfs1uMxrbNt3WLdJPOqbwAzCOxJerJlnYAOYf6 Hb0c4Kz+7Sh3Vcp2kkUvNwlKpFErHkpymtVbopmWienC8p+V/fzAN0l7/191lpOpTMBs +rz2REtw4zJL625pHqT9jJmE3Zzpa1z3Xa0KhLTGSiZbHYZ9fRoQs+StufX5H2behoGX UTrg== X-Gm-Message-State: AGi0PubnIpb3T/JpXiL6aG4iS2E5M3tJkafE3+uDPIh57VShD1R/EenH t0BTrDJfME/zmgxPN4RthnLpLw== X-Google-Smtp-Source: APiQypKmU9nNveadjSgHFcpM3Jm4Kj3E5BfAeD4Mbah/ikigh6va838vMDKjRyV01ZVC+hZXYYZIhg== X-Received: by 2002:a1c:96c6:: with SMTP id y189mr2544786wmd.106.1586791968512; Mon, 13 Apr 2020 08:32:48 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id y7sm15834662wrq.54.2020.04.13.08.32.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Apr 2020 08:32:47 -0700 (PDT) Date: Mon, 13 Apr 2020 17:32:46 +0200 From: Tomas Vondra To: Tom Lane Cc: Kamil =?utf-8?B?Sm/FhGNh?= , pgsql-bugs@lists.postgresql.org Subject: Re: backend crash Message-ID: <20200413153246.r5amtd62cxvwlqkn@development> References: <87imi37spc.fsf@alfa.kjonca> <20200413114147.a42vf3tr3auybdtr@development> <394.1586790061@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <394.1586790061@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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: QUERY PLAN ----------------------------------------------------------------------------------------------------------------------------------------------------- Finalize Aggregate (cost=315448.35..315448.36 rows=1 width=8) (actual time=18685.398..18685.400 rows=1 loops=1) -> Gather (cost=315447.52..315448.33 rows=8 width=8) (actual time=18683.862..18687.698 rows=8 loops=1) Workers Planned: 8 Workers Launched: 7 -> Partial Aggregate (cost=314447.52..314447.53 rows=1 width=8) (actual time=18669.777..18669.781 rows=1 loops=8) -> Result (cost=0.00..299447.50 rows=12500000 width=40) (actual time=0.160..17844.793 rows=250000 loops=8) -> ProjectSet (cost=0.00..80697.50 rows=12500000 width=32) (actual time=0.145..14854.132 rows=250000 loops=8) -> Parallel Seq Scan on log (cost=0.00..16947.50 rows=125000 width=81) (actual time=0.026..343.471 rows=125000 loops=8) Filter: (account = 'onet'::text) Planning Time: 0.223 ms Execution Time: 18687.862 ms (11 rows) but still no crashes. I've even built from the exact 12.2 commit to make sure the bug was not accidentally fixed by some commit since then. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services