Re: JIT breaks PostGIS

From: Andres Freund <andres(at)anarazel(dot)de>
To: Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: JIT breaks PostGIS
Date: 2018-07-21 20:25:43
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2018-07-21 23:14:47 +0300, Darafei "Komяpa" Praliaskouski wrote:
> Today I spent some time closing PostGIS tickets in preparation to Monday's
> release.
> One of the blockers,, was filed
> by Postgres APT repository maintainer Christoph Berg who noticed a test
> suite failure on Debian Stretch with Postgres 11.
> Upon investigation we found:
> - A build for Ubuntu Bionic installed on Debian Stretch passes the suite,
> requiring llvm6;
> - A build for Debian Stretch fails the suite on a call to external library
> GEOS, showing no traces of JIT in the stacktrace;
> - Setting jit=off lets the suite pass;
> - The query called in clean session by itself does not crash Postgres.
> Queries above it are required to reproduce the crash;
> - The crash affects not only Stretch, but customly collected Postgres 11 /
> clang 3.9 on Travis CI running Ubuntu Trusty:
> I suspect that a fix would require to bisect llvm/clang version which stops
> showing this behavior and making it a new minimum for JIT, if this is not a
> symptom of bigger (memory management?) problem.

Could you attempt to come up with a smaller reproducer?


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2018-07-21 20:29:49 Re: Make foo=null a warning by default.
Previous Message Fabien COELHO 2018-07-21 20:23:14 Re: Make foo=null a warning by default.