Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.6.0, 7.2.3
-
Untriaged
-
0
-
No
Description
With a query containing GROUP BY and/or aggregation, when there are multiple indexes available that can do group aggregates pushdown, the cost-based optimizer (CBO) currently always chooses the index with the "maximum" pushdown, e.g., it'll choose an index with full group/aggregate pushdown over an index with partial group/aggregate pushdown, regardless of cost. This can result in an inefficient index being chosen.
Attachments
For Gerrit Dashboard: MB-59847 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
201730,2 | MB-59847 Handle index group aggregates pushdown properly in CBO | trinity | query | Status: MERGED | +2 | +1 |
201799,2 | MB-59847 Handle index group aggregates pushdown properly in CBO | neo | query | Status: MERGED | +2 | +1 |