aboutsummaryrefslogtreecommitdiff
path: root/src/backend/jit/llvm/llvmjit_error.cpp
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2018-03-26 12:57:19 -0700
committerAndres Freund <andres@anarazel.de>2018-03-26 12:57:19 -0700
commit32af96b2b118cd204ca809d7c48c7f8ea7f879cf (patch)
treed9a09cc42afb193293a0b65cfa080d676763d776 /src/backend/jit/llvm/llvmjit_error.cpp
parent64f85894ad2730fb1449a8e81dd8026604e9a546 (diff)
downloadpostgresql-32af96b2b118cd204ca809d7c48c7f8ea7f879cf.tar.gz
postgresql-32af96b2b118cd204ca809d7c48c7f8ea7f879cf.zip
JIT tuple deforming in LLVM JIT provider.
Performing JIT compilation for deforming gains performance benefits over unJITed deforming from compile-time knowledge of the tuple descriptor. Fixed column widths, NOT NULLness, etc can be taken advantage of. Right now the JITed deforming is only used when deforming tuples as part of expression evaluation (and obviously only if the descriptor is known). It's likely to be beneficial in other cases, too. By default tuple deforming is JITed whenever an expression is JIT compiled. There's a separate boolean GUC controlling it, but that's expected to be primarily useful for development and benchmarking. Docs will follow in a later commit containing docs for the whole JIT feature. Author: Andres Freund Discussion: https://postgr.es/m/20170901064131.tazjxwus3k2w3ybh@alap3.anarazel.de
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_error.cpp')
0 files changed, 0 insertions, 0 deletions