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, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: Failed assertion with jit enabled |
Date: | 2025-02-05 18:07:58 |
Message-ID: | 911496.1738778878@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 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.)
> As a default I also always use "maintainer-clean" but it looks like it does not
> remove llvmjit.so from the installation directory: is that a miss?
Our "make install" doesn't attempt to remove any files, and I don't
believe that's customary for anyone else either. It'd be pretty
dangerous when installing into a shared system directory.
My personal development cycle usually includes "rm -rf $INSTALLDIR"
before "make install", if I've done any not-localized changes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2025-02-05 18:13:25 | Re: RFC: Additional Directory for Extensions |
Previous Message | Álvaro Herrera | 2025-02-05 17:58:54 | Re: Failed assertion with jit enabled |