Horton

Skip not SOAP-supported indexes while transforming an OR clause into SAOP

Alexander Korotkov <akorotkov@postgresql.org>

View on postgr.es
Commit: 5bba0546eecb32f4ff9388815727304823940ef6
Author: Alexander Korotkov <akorotkov@postgresql.org>
Date: 2024-11-29T07:52:12Z
Releases: 18.0 
Skip not SOAP-supported indexes while transforming an OR clause into SAOP

There is no point in transforming OR-clauses into SAOP's if the target index
doesn't support SAOP scans anyway.  This commit adds corresponding checks
to match_orclause_to_indexcol() and group_similar_or_args().  The first check
fixes the actual bug, while the second just saves some cycles.

Reported-by: Alexander Lakhin
Discussion: https://postgr.es/m/8174de69-9e1a-0827-0e81-ef97f56a5939%40gmail.com
Author: Alena Rybakina
Reviewed-by: Ranier Vilela, Alexander Korotkov, Andrei Lepikhov

Files

PathChange+/−
src/backend/optimizer/path/indxpath.c modified +9 −2
src/test/regress/expected/create_index.out modified +18 −0
src/test/regress/sql/create_index.sql modified +6 −0

Discussion