Horton
Menu

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

Yaroslav Syrytsia <me@ys.lc>

View thread
From: Yaroslav Syrytsia <me@ys.lc>
To: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>, y@lll.gd <y@lll.gd>, pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Date: 2025-07-18T10:36:41Z
Lists: pgsql-bugs 
Hello,

I just made a fresh build:
commit 91ad1bdef8e46983d82d2723c6e1c05e004f74c5 (HEAD -> 17_stable, origin/REL_17_STABLE)
Author: Dean Rasheed <dean.a.rasheed@gmail.com>
Date: Fri Jul 18 10:01:31 2025 +0100

Fix concurrent update trigger issues with MERGE in a CTE.
Can confirm that the issue is resolved now.
Thanks!
Yaroslav.
On Jul 18 2025, at 11:19 am, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> On Thu, 17 Jul 2025 at 07:46, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> >
> > I'll push this in a day or so in any case, since it's clearly fixing
> > *an* issue, even if it doesn't entirely fix the OP's issue.
> >
>
> Pushed.
> Regards,
> Dean
>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix concurrent update trigger issues with MERGE in a CTE.

  2. Stamp 17.5.

  3. Fix concurrent update issues with MERGE.