From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL 12, JIT defaults |
Date: | 2018-10-08 15:15:19 |
Message-ID: | 8A4035A9-909B-4BB4-BC24-D1971DB65219@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On October 8, 2018 8:10:45 AM PDT, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>
>On October 8, 2018 8:03:56 AM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This seems, at best, rather user-unfriendly.
>>And it's not like our conventions for other compile-option-affected
>>GUCs, eg the SSL ones.
>
>That was intentional, even though it perhaps should be better
>documented. That allows a distro to build and distribute pg without
>llvm enabled, but then have the JIT package with all the dependencies
>separately. The pg yum packages do so.
There's a function for checking whether JIT is actually available, BTW. pg_jit_available(). That also works if somebody installs an extension that's not ours (by setting jit_provider = ...).
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2018-10-08 15:16:06 | Re: PostgreSQL 12, JIT defaults |
Previous Message | Andres Freund | 2018-10-08 15:10:45 | Re: PostgreSQL 12, JIT defaults |