Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.1.4, 7.2.0
-
Untriaged
-
0
-
Unknown
Description
When CBO considers intersect scan from multiple indexes, it currently always pick an index with either order pushdown or early order. For order pushdown this is ok since we only do order pushdown if index has exact spans (no false positives). For early order we should not always prefer an index with early order, since it is possible that there are additional filters that can filter out results from the index scan, and we could have another more selective index that can be used.
Issue | Resolution |
When appropriate optimizer statistics were used in Cost-Based Optimizer (CBO), for a query with ORDER BY, if there were multiple indexes available for the query, CBO unconditionally favored an index that provided ordering. Such indexes were not always the best ones to use. | CBO now allows cost-based comparison of indexes. |