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

From Alexander Lakhin
Subject Re: BUG #17995: Segmentation fault caused by UPDATE statement
Date
Msg-id 68148dac-a574-f421-2905-51ebde2fe000@gmail.com
Whole thread Raw
In response to Re: BUG #17995: Segmentation fault caused by UPDATE statement  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17995: Segmentation fault caused by UPDATE statement  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Hello,

24.06.2023 22:51, Tom Lane wrote:
> Hmm, I don't think this is about the UPDATE per se, it's about
> not having a stack depth check in TParserGet() :-(

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/

(It looks like this issue was not discovered there because TParserGet()
doesn't call itself directly.)

Best regards,
Alexander



pgsql-bugs by date:

Previous
From: Willian Colognesi
Date:
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement
Next
From: jian he
Date:
Subject: range canonicalization function make corner case failed.