From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: JIT compiling with LLVM v11 |
Date: | 2018-03-12 15:21:36 |
Message-ID: | f6c72d9c-8b1c-cc1c-258b-7dcf9bdd3952@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/11/18 14:25, Andres Freund wrote:
>> It's perhaps a bit confusing that some of the jit_* settings take effect
>> at plan time and some at execution time. At the moment, this mainly
>> affects me reading the code ;-), but it would also have some effect on
>> prepared statements and such.
> Not quite sure what you mean?
I haven't tested this, but what appears to be the case is that
SET jit_above_cost = 0;
PREPARE foo AS SELECT ....;
SET jit_above_cost = infinity;
EXECUTE foo;
will use JIT, because jit_above_cost applies at plan time, whereas
SET jit_expressions = on;
PREPARE foo AS SELECT ....;
SET jit_expressions = off;
EXECUTE foo;
will *not* use JIT, becaue jit_expressions applies at execution time.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Darafei Komяpa Praliaskouski | 2018-03-12 15:24:36 | Re: Cast jsonb to numeric, int, float, bool |
Previous Message | Pavel Stehule | 2018-03-12 15:06:53 | Re: Transform for pl/perl |