From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: zuming.jiang@inf.ethz.ch
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement
Date: Sun, 25 Jun 2023 06:00:00 +0300
Message-ID: <68148dac-a574-f421-2905-51ebde2fe000@gmail.com> (raw)
In-Reply-To: <285547.1687636319@sss.pgh.pa.us>
References: <17995-9f20ff3e6389db4c@postgresql.org>
<285547.1687636319@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: exclusion@gmail.com, tgl@sss.pgh.pa.us, zuming.jiang@inf.ethz.ch, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement
In-Reply-To: <68148dac-a574-f421-2905-51ebde2fe000@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox