-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-106983 shows an example where we can only push one of the two eligible predicates down into the index scan because the index is multikey. It might be that one of the predicates is more selective than the other, thus resulting in a different plan. However, right now we just pick the first one in the iteration order. We should enumerate both plans so that we can pick the better one. This isn't restricted to or pushdown, however. See this test case - we should also be able to enumerate the plan that has bounds on a.c and d.f.
- related to
-
SERVER-106983 Investigate instability in plan selection for certain queries
-
- In Code Review
-
-
SERVER-16042 Optimise $all/$and to select smallest subset as initial index bounds
-
- Closed
-