Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uyo1j-00CyFl-Q8 for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 17 Sep 2025 09:00:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uyo1h-005lTi-AP for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 17 Sep 2025 09:00:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uyo1h-005lTa-0K for pgsql-pkg-debian@lists.postgresql.org; Wed, 17 Sep 2025 09:00:33 +0000 Received: from mail-ua1-x931.google.com ([2607:f8b0:4864:20::931]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uyo1f-000sAT-1J for pgsql-pkg-debian@lists.postgresql.org; Wed, 17 Sep 2025 09:00:32 +0000 Received: by mail-ua1-x931.google.com with SMTP id a1e0cc1a2514c-8943501ba3dso3344463241.3 for ; Wed, 17 Sep 2025 02:00:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758099631; x=1758704431; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=q/zYfiyiIK65Os/dfJCiFMN0G85bfJsJconaS73AN6Y=; b=kaaIHCM0pTNfxeUhIEsx4f5oZ2eYCoqbPdz4ja4ldjikSumNAm8ppMG2zg2Qb7F3uB 7evy+ZJWVysLpSVJq1FzogtKjPsfIxjBdw6pRdi/PKX0BV18rbZJy2bHi1K/I6LRiKUM 0nVIKNSey1uiC9GouQqpYCo+KCaaozAc3QVPQ1+wkkeyMi/Togy4aGFCjcLPvKf/cd+9 anjRoQWBOBoZDpfCRNPCaIHIJhKJHYeIbW+nsXcS78mTzLEvV5xo9THXszDFkJHECCDH vSGXARXioa4C6Y8YZF3faf1otxgHd6EcLZiXFdEcdvKT2eLUlO8T/ZkaY4N6Mi2iaBZj yr1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758099631; x=1758704431; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=q/zYfiyiIK65Os/dfJCiFMN0G85bfJsJconaS73AN6Y=; b=P53/wmkz33VdAaCkyOmNkqZNIyw/XYEEKB8cRyzGS/MM7ZserXP1cqTFtJ24CC/1x2 eXLXWZPFTmufL6lcpH+4SVSI8YtBav5ywunx/TQk58Z9xg+Pk39VYnq2Gg9v/2ZITWl2 db+cJUIBzUBVmWEwu/O7VfjIDy0IYpbXlAhRSFmD6IffricIUQuZIgPnDGZNXtCnzAla nC4ZqEvfV8/dnGl1yao65n6mMxL+zIsKFjjr6we1ynQ9muaZOLqkpbXHjOFZlSpqsUHR /Rux18C6gmGrlM2SXk4EvwyrLqTiwdT2lnB3+yshIcGRD8eWJG/VeWqZxgxqqK6PMUxF Stew== X-Gm-Message-State: AOJu0YzRBefDQ+zaH+So/Vya1TsyShD+6XYJ15fK+WG2XBMOwNKCrXF4 7Mf7qKLVxDTe7+ulYFwjDwQYAbKYua8L7eNlVZnJWesdYoSrvNZ8TWo0tS/pWFfU4sCmeMEPmsy twcwR0Ss7QVqZPW6lDLDcJzDuZsY2XGJkamkR X-Gm-Gg: ASbGncuORAuscAWRJuYbyOOE31HbSBEEVJ8Sbjb95grYBsSHA4KUS62HBWL9822ncar wQ2zAOp1rQ5HzbvbU8O5edqs8znbwH+zK16rUn/eNh/WhClZZXcktpP6HUJW67dp5coYzqqIzZH GmFENOvv5VQsP53a4u5dLClAxy7eKtIz7pHWdDpgs8yrVMstD1/HDy4axsZIUsIeOfx/F+3W6YI ZoTTkpL X-Google-Smtp-Source: AGHT+IFaPia5J88lehg3Q/J1YcH/Q5LiVe3jZU2xdvGQVyg7RrThK2iAbJyeOa90fkb6usbxxXZkzlrtXV/dyQaFikk= X-Received: by 2002:a05:6122:1e13:b0:544:7949:d36b with SMTP id 71dfb90a1353d-54a609f9454mr405631e0c.7.1758099630457; Wed, 17 Sep 2025 02:00:30 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?0K/RgNC+0YHQu9Cw0LIg0JzQuNC90LjQvQ==?= Date: Wed, 17 Sep 2025 11:00:20 +0200 X-Gm-Features: AS18NWDb1hQEC2oYYU00-9iCq_rAvY31Ev8zLZcL1KR95TKcZ3YWUeoiRTGsWD4 Message-ID: Subject: postgis 3.0.0 incompatibility with LLVM 15 To: pgsql-pkg-debian@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000f409ea063efb77b5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f409ea063efb77b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello! Versions: OS: Ubuntu 22.04 PostgreSQL 15.3 (Ubuntu 15.3-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, 64-bit POSTGIS=3D"3.6.0 4c1967d" [EXTENSION] PGSQL=3D"150" GEOS=3D"3.10.2-CAPI-1.1= 6.0" SFCGAL=3D"SFCGAL 1.4.1, CGAL 5.3.1, BOOST 1.74.0" PROJ=3D"8.2.1 NETWORK_ENABLED=3DOFF URL_ENDPOINT=3Dhttps://cdn.proj.org USER_WRITABLE_DIRECTORY=3D/tmp/proj DATABASE_PATH=3D/usr/share/proj/proj.db= " (compiled against PROJ 8.2.1) GDAL=3D"GDAL 3.4.1, released 2021/12/27" LIBX= ML=3D "2.9.13" LIBJSON=3D"0.15" LIBPROTOBUF=3D"1.3.3" WAGYU=3D"0.5.0 (Internal)" = RASTER After upgrading PostGIS from 3.3.0 to 3.6.0 (latest) most of our queries result in the following error: *error: Not an int attribute (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.0')= * . PostGIS was installed using *sudo apt-get install postgis postgresql-15-postgis-3*. It seems the problem is JIT using LLVM 14. LLVM on my PostgreSQL instance is *'LLVM_CONFIG=3D/usr/bin/llvm-config-15'*. Setting JIT=3Doff solves the problem but we have quite many scenarios where using JIT is let=E2=80=99s say prefferable. So the question is is it possible to make PostGIS 3.3.0 compatible with my PostgreSQL with JIT on? -- Sincerely, Yaras --000000000000f409ea063efb77b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello!

Versions:
OS: Ubuntu 22.04

PostgreSQL 15.3 (Ubuntu 15.3-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, 64-bit

POSTGIS=3D"3.6.= 0 4c1967d" [EXTENSION] PGSQL=3D"150&quo= t; GEOS=3D"3.10.2-CAPI-1.16.= 0" SFCGAL=3D"SFCGAL 1.4= .1, CGAL 5.3.1, BOOST 1.74.0" PROJ=3D"8.2.1 NETWORK_ENABLED=3DOFF URL_ENDPOINT=3Dhttps://cdn.proj.org US= ER_WRITABLE_DIRECTORY=3D/tmp/proj DATABASE_PATH=3D/usr/share/proj/proj.db&q= uot; (compiled against PROJ 8.2.1= ) GDAL=3D"GDAL 3.4.1, releas= ed 2021/12/27" LIBXML=3D&quo= t;2.9.13" LIBJSON=3D"0.= 15" LIBPROTOBUF=3D"1.3.= 3" WAGYU=3D"0.5.0 (Inte= rnal)" RASTER


After upgrading PostGIS from 3.3.0 to 3.6.0 (latest) most of our q= ueries result in the following error:
error= : Not an int attribute (Producer: 'LLVM15.0.7' Reader: 'LLVM 14= .0.0').

P= ostGIS was installed using=C2=A0sudo apt-get install postgis postgr= esql-15-postgis-3.

It seems the problem is JIT using LLVM 14.=C2=A0LLVM on my PostgreSQL= instance is=C2=A0'LLVM_CONFIG=3D/usr/bin/llvm-config-15'.= =C2=A0

Setting=C2=A0JI= T=3Doff solves the problem but we have quite many scenarios where using JIT= is let=E2=80=99s say prefferable.

So the question is is it possible to make PostGIS 3.3.0 compat= ible with my PostgreSQL with JIT on?

--
Sincerely,
Yaras
--000000000000f409ea063efb77b5--