From: 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: Sat, 24 Jun 2023 15:51:59 -0400
Message-ID: <285547.1687636319@sss.pgh.pa.us> (raw)
In-Reply-To: <17995-9f20ff3e6389db4c@postgresql.org>
References: <17995-9f20ff3e6389db4c@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> --- Test case ---
> create table t1 (pkey int4, c7 float8, c8 text, c9 float8);
> insert into t1 (pkey, c7, c8, c9) values (96000, 0.0, '3n@', -79.14);
> update t1 set c7 = t1.c9 / t1.c7 where 'a' @@ repeat(t1.c8, t1.pkey);
Hmm, I don't think this is about the UPDATE per se, it's about
not having a stack depth check in TParserGet() :-(
regards, tom lane
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: 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: <285547.1687636319@sss.pgh.pa.us>
* 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