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 1kUErQ-0000QD-2n for pgsql-bugs@arkaria.postgresql.org; Sun, 18 Oct 2020 20:00:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kUErO-00083Y-50 for pgsql-bugs@arkaria.postgresql.org; Sun, 18 Oct 2020 20:00:54 +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 1kUErN-000814-7C for pgsql-bugs@lists.postgresql.org; Sun, 18 Oct 2020 20:00:53 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kUErK-0004jM-UX for pgsql-bugs@postgresql.org; Sun, 18 Oct 2020 20:00:51 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09IK0hUK235510; Sun, 18 Oct 2020 16:00:44 -0400 From: Tom Lane To: pinker cc: pgsql-bugs@postgresql.org Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines In-reply-to: <1603050580276-0.post@n3.nabble.com> References: <1603050466566-0.post@n3.nabble.com> <1603050580276-0.post@n3.nabble.com> Comments: In-reply-to pinker message dated "Sun, 18 Oct 2020 12:49:40 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <235508.1603051243.1@sss.pgh.pa.us> Date: Sun, 18 Oct 2020 16:00:43 -0400 Message-ID: <235509.1603051243@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk pinker writes: > Do you need any futher details? Yes. The stack trace is interesting, but far from enough to solve the problem. Since it evidently is reproducible for you, maybe you could extract a self-contained test case? regards, tom lane