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

From Willian Colognesi
Subject Re: BUG #17995: Segmentation fault caused by UPDATE statement
Date
Msg-id CADAf1kbuz_tzWCOzYyqEsRnxmDS6GV_VLP7QanZzqtyuUAONTA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17995: Segmentation fault caused by UPDATE statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
A time ago I had a problem with segmentation fault, and it was solved disabling jit.


On Sat, Jun 24, 2023, 16:52 Tom Lane <tgl@sss.pgh.pa.us> wrote:
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


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement