diff options
| author | David Rowley <drowley@postgresql.org> | 2022-08-02 11:02:46 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2022-08-02 11:02:46 +1200 |
| commit | b592422095655a64d638f541df784b19b8ecf8ad (patch) | |
| tree | ae3e06d77ac1efcfd7972c36705bbe1e0bd01d34 /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | 2865b4060a434855f90fda41f1b8f4bca7c55b0e (diff) | |
| download | postgresql-b592422095655a64d638f541df784b19b8ecf8ad.tar.gz postgresql-b592422095655a64d638f541df784b19b8ecf8ad.zip | |
Relax overly strict rules in select_outer_pathkeys_for_merge()
The select_outer_pathkeys_for_merge function made an attempt to build the
merge join pathkeys in the same order as query_pathkeys. This was done as
it may have led to no sort being required for an ORDER BY or GROUP BY
clause in the upper planner. However, this restriction seems overly
strict as it required that we match the query_pathkeys entirely or we
don't bother putting the merge join pathkeys in that order.
Here we relax this rule so that we use a prefix of the query_pathkeys
providing that prefix matches all of the join quals. This may provide the
upper planner with partially sorted input which will allow the use of
incremental sorts instead of full sorts.
Author: David Rowley
Reviewed-by: Richard Guo
Discussion: https://postgr.es/m/CAApHDvrtZu0PHVfDPFM4Yx3jNR2Wuwosv+T2zqa7LrhhBr2rRg@mail.gmail.com
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions