Re: BUG #17995: Segmentation fault caused by UPDATE statement

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, zuming(dot)jiang(at)inf(dot)ethz(dot)ch, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement
Date: 2023-06-26 04:21:47
Message-ID: ZJkSW1F78yDV2bjl@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-06-26 04:27:08 Re: BUG #17995: Segmentation fault caused by UPDATE statement
Previous Message 梁 成林 2023-06-26 03:53:28 回复: BUG #17998: Postgres crashes when executing WorkTableScan.