Horton

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

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, zuming.jiang@inf.ethz.ch, pgsql-bugs@lists.postgresql.org
Date: 2023-06-26T04:21:47Z
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

Commits

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

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