Issue after upgrading postgis to 3.4.2

[Regina Obe]

Which system are you on?  A apt or Yum based?

 

It sounds like maybe you are picking up LLVM from your OS repo, and bits from the PGDG repo.

 

You should probably disable your OS repo LLVM

 

Or report issue to

 

https://www.postgresql.org/list/pgsql-pkg-yum/  (CentOS / Redhat / Rocky)

 

or

 

https://www.postgresql.org/list/pgsql-pkg-debian/  (Debian/Ubuntu)

 

 

At anyrate I don’t think PostGIS group can do anything about this as we don’t explicitly turn on/off JIT.

 

As far as PostGIS workload is concerned, so people have mentioned JIT is pretty useless, and often better to keep it off to not make it try to optimize stupid things.

But what I heard was way back when it was a new thing, so I think at least now, it’s less likely to do harm turned on.

 

Hope that helps,

Regina

 

 

From: Joan <aseques at gmail.com> 
Sent: Wednesday, June 5, 2024 4:51 AM
To: postgis-users at lists.osgeo.org
Subject: Re: Issue after upgrading postgis to 3.4.2

 

I tried the workaround that was mentioned on the stack overflow thread here https://stackoverflow.com/q/76192816/322049

It mentions that disabling JIT could fix the issue

 

show jit; --equals to ON
alter database top set jit=off;
-- reconnect to db
show jit; --equals to off

With jit == off the query runs without issues, still i doesn't seem the appropiate thing to do, and on the replica system there's no need to disable the JIT.

Shall I open a bug?

 

Missatge de Joan <aseques at gmail.com <mailto:aseques at gmail.com> > del dia dt., 4 de juny 2024 a les 18:00:

I have recently upgraded the postgis and pgrouting extensions on a server via the pgdg repository from 3.3.1 to 3.4.2, this are my current versions (the exact same versions are installed on another server with and older copy of the database without the same synthoms)

                                         
       Name       | Version |   Schema    
------------------+---------+-------------
 pgrouting        | 3.6.2   | public     
 plpgsql          | 1.0     | pg_catalog 
 postgis          | 3.4.2   | public     
 postgis_raster   | 3.4.2   | public     
 postgis_topology | 3.4.2   | topology   
 tds_fdw          | 2.0.3   | public     

 

When I call this query

 

select *
FROM topo.arcs t,
topo.nodes n
where
t.geom is not null
and n.geom is not null
and ST_DWithin(ST_StartPoint(t.geom), n.geom, 0.01)

 

On the sql program (even local console):

SQL Error [08006]: An I/O error occurred while sending to the backend.

On the postgres logs I see this line though:

error: Not an int attribute (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.0')

 

 

On a stackoverflow I found a mention that this could be related to the JIT compilation 

and suggested disabling it, but I'd like to investigate more before doing so 

 

Any pointers will be appreciated,

 

Thanks, 

 

Joan

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20240605/e910adb3/attachment.htm>