Re: BUG #17737: An assert failed in execExprInterp.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: xinwen(at)stu(dot)scu(dot)edu(dot)cn, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17737: An assert failed in execExprInterp.c
Date: 2023-01-05 21:33:48
Message-ID: 2828934.1672954428@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> I'm kind of baffled as to how it's escaped detection for this long;
> maybe the assertion is overly tight, and the case actually works
> in non-assert builds?

A quick test says that indeed this example works in a non-assert
build. So that may explain the lack of previous reports. Whether
it'd be okay to weaken this check across-the-board isn't clear to me.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2023-01-05 21:41:49 Re: BUG #17737: An assert failed in execExprInterp.c
Previous Message Tom Lane 2023-01-05 20:50:03 Re: BUG #17737: An assert failed in execExprInterp.c