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

From Tom Lane
Subject Re: BUG #17995: Segmentation fault caused by UPDATE statement
Date
Msg-id 285547.1687636319@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17995: Segmentation fault caused by UPDATE statement  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17995: Segmentation fault caused by UPDATE statement  (Willian Colognesi <willian_colognesi@trimble.com>)
Re: BUG #17995: Segmentation fault caused by UPDATE statement  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-bugs
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: PG Bug reporting form
Date:
Subject: BUG #17995: Segmentation fault caused by UPDATE statement
Next
From: Willian Colognesi
Date:
Subject: Re: BUG #17995: Segmentation fault caused by UPDATE statement