Transform OR-clauses to SAOP's during index matching
authorAlexander Korotkov <akorotkov@postgresql.org>
Sat, 23 Nov 2024 23:40:20 +0000 (01:40 +0200)
committerAlexander Korotkov <akorotkov@postgresql.org>
Sat, 23 Nov 2024 23:40:20 +0000 (01:40 +0200)
commitd4378c0005e61b1bb78e88097ea6efcdddbe2d6e
tree7b1d55b537b5a809c668a2413c119d359063ad60
parent869ee4f10eca2acda3d2210198a46d5029a569fc
Transform OR-clauses to SAOP's during index matching

This commit makes match_clause_to_indexcol() match
"(indexkey op C1) OR (indexkey op C2) ... (indexkey op CN)" expression
to the index while transforming it into "indexkey op ANY(ARRAY[C1, C2, ...])"
(ScalarArrayOpExpr node).

This transformation allows handling long OR-clauses with single IndexScan
avoiding diving them into a slower BitmapOr.

We currently restrict Ci to be either Const or Param to apply this
transformation only when it's clearly beneficial.  However, in the future,
we might switch to a liberal understanding of constants, as it is in other
cases.

Discussion: https://postgr.es/m/567ED6CA.2040504%40sigaev.ru
Author: Alena Rybakina, Andrey Lepikhov, Alexander Korotkov
Reviewed-by: Peter Geoghegan, Ranier Vilela, Alexander Korotkov, Robert Haas
Reviewed-by: Jian He, Tom Lane, Nikolay Shaplov
src/backend/optimizer/path/indxpath.c
src/test/regress/expected/create_index.out
src/test/regress/expected/join.out
src/test/regress/expected/rowsecurity.out
src/test/regress/expected/stats_ext.out
src/test/regress/expected/uuid.out
src/test/regress/sql/create_index.sql
src/test/regress/sql/join.sql
src/test/regress/sql/rowsecurity.sql
src/test/regress/sql/stats_ext.sql
src/test/regress/sql/uuid.sql