Horton

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

Alexander Law <exclusion@gmail.com>

View thread View on postgr.es
From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, zuming.jiang@inf.ethz.ch
Cc: pgsql-bugs@lists.postgresql.org
Date: 2023-06-25T03:00:00Z
Lists: 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

Commits

  1. Check for interrupts and stack overflow in TParserGet().

  2. Doc: Clarify the behavior of triggers/rules in a logical subscriber.