From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | buschmann(at)nidsa(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17943: Undefined symbol LLVMBuildGEP in llvmjit.so during pg_restore |
Date: | 2023-05-25 03:20:44 |
Message-ID: | CA+hUKGLXzYAhYjXETo881LqabH9eaAzqGT2GMkdvEkNMp9MUWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-pkg-yum |
On Thu, May 25, 2023 at 4:19 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:>
> Any clues?
Is it possible that whoever packaged that compiled it against LLVM 15
but then put LLVM 16 into the package depencencies? I'm not a Fedora
user so that might be a silly question... but do you still have the
ability to install LLVM 15? Unfortunately PostgreSQL can't use LLVM16
yet, because we need to make some changes (hopefully in the next point
release):
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2023-05-25 04:07:59 | Re: BUG #17942: vacuumdb doesn't populate extended statistics on partitioned tables |
Previous Message | David G. Johnston | 2023-05-24 16:58:50 | Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN |
From | Date | Subject | |
---|---|---|---|
Next Message | Hans Buschmann | 2023-05-25 07:30:58 | AW: BUG #17943: Undefined symbol LLVMBuildGEP in llvmjit.so during pg_restore |
Previous Message | PG Bug reporting form | 2023-05-24 13:28:46 | BUG #17943: Undefined symbol LLVMBuildGEP in llvmjit.so during pg_restore |