, 2025 6:49 AM
To: postgis-users
Subject: backend error after upgrading to 3.6.0
I guess I found the issue. Seems like every time I send queries using PostGIS
functions I get the following error:
error: Not an int attribute (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.0'
I guess I found the issue. Seems like every time I send queries using PostGIS
functions I get the following error:
error: Not an int attribute (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.0')
The very first time it appeared is after upgrading PostGIS to 3.6.0. LLVM on my
PostgreSQL instance is
: postgis-users
Subject: backend error after upgrading to 3.6.0
- Versions:
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="3.6.0 4c1967d" [EXTENSION] PGSQL="150" GEOS="3.10.2-CAP
tgis-users < postgis-users@lists.osgeo.org>
>Subject: backend error after upgrading to 3.6.0
>
>I guess I found the issue. Seems like every time I send queries using PostGIS
>functions I get the following error:
>
>error: Not an int attribute (Producer: 'LLVM15.0.7'
priority settings.
>>
>>
>>From: Ярослав Минин via postgis-users < postgis-users@lists.osgeo.org >
>>Sent: Tuesday, September 16, 2025 6:49 AM
>>To: postgis-users < postgis-users@lists.osgeo.org >
>>Subject: backend error after upgrading to 3.6.0
>&
Минин
Sent: Tuesday, September 16, 2025 1:41 PM
To: Regina Obe
Cc: postgis-users
Subject: Re: RE: backend error after upgrading to 3.6.0
I've already tried and with JIT off it works.
"Also did you only upgrade PostGIS or did you upgrade PostgreSQL as well."
PostGIS only. Postgr
jit at all, I’d suggest just turning it off systemwide.
>
>
>ALTER SYSTEM set jit = off;
>SELECT pg_reload_conf();
>
>
>
>
>From: Ярослав Минин via postgis-users < postgis-users@lists.osgeo.org>
>Sent: Tuesday, September 16, 2025 10:48 AM
>To: po
- Versions:
PostgreSQL 15.3 ( Ubuntu 15.3 -1. pgdg22 . 04 + 1 ) on x86_64 - pc - linux -
gnu , compiled by gcc ( Ubuntu 11. 3.0 - 1 ubuntu1 ~ 22.04 ) 11. 3.0 , 64 -
bit
POSTGIS = "3.6.0 4c1967d" [ EXTENSION ] PGSQL = "150" GEOS =
"3.10.2-CAPI-1.16.0" SFCGAL = "SFCGAL 1.4.1, CGAL 5.3.1, BOO
> On 2025-09-15 19:16 +0200, Ярослав Минин via postgis-users wrote:
> >
> > Hello! We have stumbled upon a strange issue after upgrading from
> > PostGIS 3.3.0 to 3.6.0.
> > A simple query like select * from foo.bar where ST_IsValid(geometry)
> > executed in DBeaver returns the following error:
>
On 2025-09-15 19:16 +0200, Ярослав Минин via postgis-users wrote:
>
> Hello! We have stumbled upon a strange issue after upgrading from
> PostGIS 3.3.0 to 3.6.0.
> A simple query like select * from foo.bar where ST_IsValid(geometry)
> executed in DBeaver returns the following error:
> SQL Error [
Hello! We have stumbled upon a strange issue after upgrading from PostGIS 3.3.0
to 3.6.0.
A simple query like select * from foo.bar where ST_IsValid(geometry) executed
in DBeaver returns the following error:
SQL Error [08006]: An I/O error occurred while sending to the backend if the
size
11 matches
Mail list logo
