From: Tom Lane <tgl@sss.pgh.pa.us>
To: y@lll.gd
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
Date: Tue, 15 Jul 2025 14:13:53 -0400
Message-ID: <937261.1752603233@sss.pgh.pa.us> (raw)
In-Reply-To: <18986-e7a8aac3d339fa47@postgresql.org>
References: <18986-e7a8aac3d339fa47@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, y@lll.gd, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
In-Reply-To: <937261.1752603233@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox