Re: BUG #17995: Segmentation fault caused by UPDATE statement - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17995: Segmentation fault caused by UPDATE statement
Date
Msg-id ZJkSW1F78yDV2bjl@paquier.xyz
Whole thread Raw
In response to Re: BUG #17995: Segmentation fault caused by UPDATE statement  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: BUG #17995: Segmentation fault caused by UPDATE statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Sun, Jun 25, 2023 at 06:00:00AM +0300, Alexander Lakhin wrote:
> BTW, there is a commitfest entry to eliminate a bunch of other stack
> overflow hazards (may be the fuzzer can find some of them too):
> https://commitfest.postgresql.org/43/4239/

Thanks for the pointer, I'll double-check that.  Some of the locations
of stack depth checks proposed involve performance-sensitive code
paths, though, like mcxt.c :/
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: 梁 成林
Date:
Subject: 回复: BUG #17998: Postgres crashes when executing WorkTableScan.
Next
From: Tom Lane
Date:
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement