diff options
| author | David Rowley <drowley@postgresql.org> | 2023-10-13 01:13:36 +1300 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2023-10-13 01:13:36 +1300 |
| commit | 1e81d3e6e0a0e35e52e109742c5ce3738c3e87c6 (patch) | |
| tree | b57fa306cb90e294dabf921abda32626e53d47bd /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | 245e0f4e8de565ec87c1ec64bfd89d846f3d496e (diff) | |
| download | postgresql-1e81d3e6e0a0e35e52e109742c5ce3738c3e87c6.tar.gz postgresql-1e81d3e6e0a0e35e52e109742c5ce3738c3e87c6.zip | |
Fix runtime partition pruning for HASH partitioned tables
This could only affect HASH partitioned tables with at least 2 partition
key columns.
If partition pruning was delayed until execution and the query contained
an IS NULL qual on one of the partitioned keys, and some subsequent
partitioned key was being compared to a non-Const, then this could result
in a crash due to the incorrect keyno being used to calculate the
stateidx for the expression evaluation code.
Here we fix this by properly skipping partitioned keys which have a
nullkey set. Effectively, this must be the same as what's going on
inside perform_pruning_base_step().
Sergei Glukhov also provided a patch, but that's not what's being used
here.
Reported-by: Sergei Glukhov
Reviewed-by: tender wang, Sergei Glukhov
Discussion: https://postgr.es/m/d05b26fa-af54-27e1-f693-6c31590802fa@postgrespro.ru
Backpatch-through: 11, where runtime partition pruning was added.
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions