diff options
| author | Andres Freund <andres@anarazel.de> | 2018-03-22 11:45:07 -0700 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2018-03-22 11:51:58 -0700 |
| commit | cc415a56d09a8da7c919088036b6097b70f10791 (patch) | |
| tree | b99cb7e66041f8533dc63c4a689cbf3f03956957 /src/backend/executor/execUtils.c | |
| parent | 7ec0d80c0508eae35ac8e19d041f9ba1276de08e (diff) | |
| download | postgresql-cc415a56d09a8da7c919088036b6097b70f10791.tar.gz postgresql-cc415a56d09a8da7c919088036b6097b70f10791.zip | |
Basic planner and executor integration for JIT.
This adds simple cost based plan time decision about whether JIT
should be performed. jit_above_cost, jit_optimize_above_cost are
compared with the total cost of a plan, and if the cost is above them
JIT is performed / optimization is performed respectively.
For that PlannedStmt and EState have a jitFlags (es_jit_flags) field
that stores information about what JIT operations should be performed.
EState now also has a new es_jit field, which can store a
JitContext. When there are no errors the context is released in
standard_ExecutorEnd().
It is likely that the default values for jit_[optimize_]above_cost
will need to be adapted further, but in my test these values seem to
work reasonably.
Author: Andres Freund, with feedback by Peter Eisentraut
Discussion: https://postgr.es/m/20170901064131.tazjxwus3k2w3ybh@alap3.anarazel.de
Diffstat (limited to 'src/backend/executor/execUtils.c')
| -rw-r--r-- | src/backend/executor/execUtils.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/backend/executor/execUtils.c b/src/backend/executor/execUtils.c index a8ae37ebc80..14b07b5d449 100644 --- a/src/backend/executor/execUtils.c +++ b/src/backend/executor/execUtils.c @@ -158,6 +158,9 @@ CreateExecutorState(void) estate->es_use_parallel_mode = false; + estate->es_jit_flags = 0; + estate->es_jit = NULL; + /* * Return the executor state structure */ |