| From: | Willian Colognesi <willian_colognesi(at)trimble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | zuming(dot)jiang(at)inf(dot)ethz(dot)ch, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17995: Segmentation fault caused by UPDATE statement |
| Date: | 2023-06-24 20:48:09 |
| Message-ID: | CADAf1kbuz_tzWCOzYyqEsRnxmDS6GV_VLP7QanZzqtyuUAONTA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)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
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2023-06-25 03:00:00 | Re: BUG #17995: Segmentation fault caused by UPDATE statement |
| Previous Message | Tom Lane | 2023-06-24 19:51:59 | Re: BUG #17995: Segmentation fault caused by UPDATE statement |