Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function

From: surya poondla <suryapoondla4(at)gmail(dot)com>
To: haogangmao(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Subject: Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
Date: 2026-07-08 18:25:54
Message-ID: CAOVWO5pC-uSp2EJQDAKZ2HqZq9Zdp8UO9CAAYyZS3M1FYjW_4A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Haogangmao, Ayush

Thank you for reporting the bug.

I verified this, and yes, this is the same crash as
https://www.postgresql.org/message-id/19382-4c2060ffee72759b%40postgresql.org
that Ayush mentioned.

I am actively working on that bug, fixed most of the cases. I am exploring
some corner cases that can reproduce the crash and fixing those too.

Regards,
Surya Poondla

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2026-07-08 20:29:35 Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
Previous Message Peter Eisentraut 2026-07-08 17:14:08 Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build