Horton

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

Willian Colognesi <willian_colognesi@trimble.com>

View thread View on postgr.es
From: Willian Colognesi <willian_colognesi@trimble.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: zuming.jiang@inf.ethz.ch, pgsql-bugs@lists.postgresql.org
Date: 2023-06-24T20:48:09Z
Lists: 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
>
>
>

Commits

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

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