| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: JIT breaks PostGIS |
| Date: | 2018-07-22 18:57:01 |
| Message-ID: | 20180722185700.GC18253@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Andres Freund 2018-07-22 <20180722185106(dot)qxc5ie745tqdazgq(at)alap3(dot)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-22 19:47:58 | Re: JIT breaks PostGIS |
| Previous Message | Tom Lane | 2018-07-22 18:53:51 | Re: Non-portable shell code in pg_upgrade tap tests |