From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #17474: Segmentation fault from INSERT ( JumbleExpr ) |
Date: | 2022-05-05 14:34:40 |
Message-ID: | CAGnEbohm6ebdCbrKbwBjOERBP_+ofPdmGxY0TKeicT76Mf647A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
чт, 5 мая 2022 г. в 16:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > Quite simple setup, that works on 13 version, is causing SEGFAULTs on
> 14.2.
> > Reproducible.
>
> Can you provide a reproducer SQL script? The stack trace looks like
> some element of the VALUES list is not in the format that JumbleExpr
> is expecting, but there's nothing odd-looking about the fragment
> you showed.
>
I will try to find such a case, though it might not be straightforward.
Same query after the restart of Postgres succeeds. So it feels like we're
accumulating smth here.
--
Victor Yegorov
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-05-05 15:12:36 | Re: BUG #17474: Segmentation fault from INSERT ( JumbleExpr ) |
Previous Message | Tom Lane | 2022-05-05 13:44:40 | Re: BUG #17474: Segmentation fault from INSERT ( JumbleExpr ) |