Re: Failed assertion with jit enabled

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Failed assertion with jit enabled
Date: 2025-02-05 15:51:17
Message-ID: 813592.1738770677@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> writes:
> I was doing some tests and managed to trigger a failed assertion with jit
> enabled.

> The test can be simplified to:

> postgres=# select count(*) from generate_series(1,10000000);
> server closed the connection unexpectedly

Hmm, works for me on today's HEAD.

> The failed assertion is:
> TRAP: failed Assert("false"), File: "llvmjit_expr.c", Line: 2833, PID: 3060333

There are two Assert(false) in that file, neither of them particularly
close to line 2833 as of today, so I'm not sure what version you are
using or which one you're hitting. Nonetheless, I'll go out on a
limb and guess that this will go away if you do "git clean -dfxq"
and a full rebuild. It smells like different files getting out of
sync about the representation of ExprEvalOp or ExprEvalStep.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-02-05 16:05:15 Re: Remove unnecessary static specifier
Previous Message David G. Johnston 2025-02-05 15:45:08 Re: CREATE ROLE bug?