Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q25RH-0006sN-Rr for pgsql-bugs@arkaria.postgresql.org; Thu, 25 May 2023 07:31:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q25RG-0001QT-N7 for pgsql-bugs@arkaria.postgresql.org; Thu, 25 May 2023 07:31:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q25RG-0001QK-EP for pgsql-bugs@lists.postgresql.org; Thu, 25 May 2023 07:31:10 +0000 Received: from ma03-relay.lansolnet.com ([176.95.46.36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q25RC-001mMF-6H for pgsql-bugs@lists.postgresql.org; Thu, 25 May 2023 07:31:09 +0000 Received: from unknown ([192.168.8.231]) by ma03-relay.lansolnet.com; Thu, 25 May 2023 09:31:02 +0200 Received: from MBX200C.cloud4partner.com (192.168.8.232) by MBX200B.cloud4partner.com (192.168.8.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Thu, 25 May 2023 09:30:59 +0200 Received: from MBX200E.cloud4partner.com (192.168.8.234) by MBX200C.cloud4partner.com (192.168.8.232) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Thu, 25 May 2023 09:30:59 +0200 Received: from MBX200E.cloud4partner.com ([fe80::881b:2a52:f04f:d634]) by MBX200E.cloud4partner.com ([fe80::881b:2a52:f04f:d634%13]) with mapi id 15.01.0669.032; Thu, 25 May 2023 09:30:58 +0200 From: Hans Buschmann To: Thomas Munro , "pgsql-bugs@lists.postgresql.org" Subject: AW: BUG #17943: Undefined symbol LLVMBuildGEP in llvmjit.so during pg_restore Thread-Topic: BUG #17943: Undefined symbol LLVMBuildGEP in llvmjit.so during pg_restore Thread-Index: AQHZjkO5ermnUca6mkyX9srS7AwBB69qMbkAgABicas= Date: Thu, 25 May 2023 07:30:58 +0000 Message-ID: <69c59ffd5f8548dfa2d3f12ea5303551@nidsa.net> References: <17943-56bb8c6bd4409b9f@postgresql.org>, In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.8.240] Content-Type: multipart/alternative; boundary="_000_69c59ffd5f8548dfa2d3f12ea5303551nidsanet_" MIME-Version: 1.0 X-cloud-security-sender: buschmann@nidsa.net X-cloud-security-recipient: pgsql-bugs@lists.postgresql.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on ma03-relay.lansolnet.com with 7BF461984EB0 X-cloud-security-connect: unknown[192.168.8.231], TLS=1, IP=192.168.8.231 X-cloud-security: scantime:.6684 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_69c59ffd5f8548dfa2d3f12ea5303551nidsanet_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello Thomas, Thank you for your information about LLVM16 support. I noticed the discussion in hackers. I wanted to point out that I used the standard repositories from PGDG15. As to my knowledge they are packaged by Devrim, so this is the standard dis= tribution for RedHat-style Linux on PGDG. (This is shown by the dnf list lines in my OM) I am not trying to use LLVM on my platform (tiny data, optimized SQL etc.) = but I wanted to notice everybody that there are unreferenced symbols in llv= mjit.so, something that should not happen. I have no idea where this come from nor where it is used, but the unreferen= ced symbols should be at least masked with dummy rountines (or avoided) to = prevent the error for other users where the problem matters much more! Unfortunately this occurs on pg_restore, the ultimate backup/restore of a d= atabase, and data are not restored correctly and must be corrected manually= afterwords. Perhaps you could contact Devrim for clarification... Hans Buschmann ________________________________ --_000_69c59ffd5f8548dfa2d3f12ea5303551nidsanet_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello Thomas,


Thank you for your information about LLVM16 support.

I noticed the discussion in hackers.


I wanted to point out that I used the standard repositories from PGDG15.=

As to my knowledge they are packaged by Devrim, so this is the standard = distribution for RedHat-style Linux on PGDG.

(This is shown by the dnf list lines in my OM)


I am not trying to use LLVM on my platform (tiny data, optimized SQL etc= .) but I wanted to notice everybody that there are unreferenced symbols in = llvmjit.so, something that should not happen.


I have no idea where this come from nor where it is used, but the unrefe= renced symbols should be at least masked with dummy rountines (or avoided) = to prevent the error for other users where the problem matters much more!


Unfortunately this occurs on pg_restore, the ultimate backup/restore of = a database, and data are not restored correctly and must be corrected manua= lly afterwords.


Perhaps you could contact Devrim for clarification...


Hans Buschmann



--_000_69c59ffd5f8548dfa2d3f12ea5303551nidsanet_--