Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ubkAA-004h1p-OX for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Jul 2025 18:13:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ubkA8-004MRC-IE for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Jul 2025 18:13:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ubkA8-004MQz-9X for pgsql-bugs@lists.postgresql.org; Tue, 15 Jul 2025 18:13:56 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ubkA6-007Ri8-0i for pgsql-bugs@lists.postgresql.org; Tue, 15 Jul 2025 18:13:56 +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 56FIDrjH937262; Tue, 15 Jul 2025 14:13:53 -0400 From: Tom Lane To: y@lll.gd cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution In-reply-to: <18986-e7a8aac3d339fa47@postgresql.org> References: <18986-e7a8aac3d339fa47@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 15 Jul 2025 16:11:56 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <937260.1752603233.1@sss.pgh.pa.us> Date: Tue, 15 Jul 2025 14:13:53 -0400 Message-ID: <937261.1752603233@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > During testing a flow in an app, I encountered a segfault that only happens > during parallel execution: > https://gist.github.com/joy4eg/708458e204f52129a8e54a13534586b7 This report isn't terribly helpful, since you have not explained how to trigger the crash. If we can't duplicate it, it's hard to decide what is the appropriate fix. regards, tom lane