Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution

From: Yaroslav Syrytsia <me(at)ys(dot)lc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
Date: 2025-07-16 09:33:33
Message-ID: 2109154296.466969.1752658413508@office-sso.mailbox.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello,

I made a small reproducer here - https://github.com/joy4eg/pg-merge-crash

It creates a few tables and then executes MERGE statements in parallel.

Yaroslav.

> On 2025-07-15 20:13 CEST Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2025-07-16 09:55:44 Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
Previous Message Michael Paquier 2025-07-16 04:45:55 Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti