Re: JIT breaks PostGIS - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: JIT breaks PostGIS
Date
Msg-id 20180722185700.GC18253@msg.df7cb.de
Whole thread Raw
In response to Re: JIT breaks PostGIS  (Andres Freund <andres@anarazel.de>)
Responses Re: JIT breaks PostGIS  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Re: Andres Freund 2018-07-22 <20180722185106.qxc5ie745tqdazgq@alap3.anarazel.de>
> > Does that mean JIT is not ready for prime time yet and should be
> > disabled in default installations? Or does it just mean that llvm 4.0
> > is old?
> 
> I don't know yet, it's probably just some small bug. But let me debug it
> first.

Sure.

The question will be coming up eventually, though, and I think the
options on the packaging side are:

1) Disable jit completely
2) Compile --with-llvm, but disable jit in the config by default
3) Compile --with-llvm, but disable jit for older llvm versions
4) Enable jit everywhere where llvm >= 3.9 is available

Option 4 is what the Debian packages implement now, but it might make
sense to go to 2 or 3 for PG11 (only).

Christoph


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Non-portable shell code in pg_upgrade tap tests
Next
From: Tom Lane
Date:
Subject: Re: JIT breaks PostGIS