From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Failed assertion with jit enabled |
Date: | 2025-02-05 19:46:05 |
Message-ID: | wy673ti43kkhtygwvfrt5rbqpzod4mcawxiijkpwla52fpksxw@icehk55yfz26 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2025-02-05 13:07:58 -0500, Tom Lane wrote:
> Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> writes:
> > I did look more closely (knowing that it works for you) and the issue is linked
> > to not using --with-llvm. Inded, I used to use --with-llvm but removed it some
> > time ago for testing.
> > So the failed build was not using --with-llvm and was relying on an old version
> > of llvmjit.so (build from the last time I used --with-llvm)...
>
> Hmm ... I don't understand why a non-JIT build of the core would
> attempt to load llvmjit.so. Seems like trouble waiting to happen,
> given how closely coupled the core and JIT are. (The .bc files are
> pretty much guaranteed to be out of sync in such a case.)
To support a) packaging postgres with split-out JIT support b) pluggability of
JIT backends, the only way we detect if JIT is supported is by trying to load
the configured JIT backend (jit_provider GUC).
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Nazir Bilal Yavuz | 2025-02-05 20:02:15 | Re: Show WAL write and fsync stats in pg_stat_io |
Previous Message | Sami Imseih | 2025-02-05 19:36:57 | Re: Prevent COPY FREEZE on Foreign tables |