-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
After SERVER-122314, our plan stability tests began choosing an index probe into lineitem causing an order of magnitude regression in the number of keys scanned in the chosen plan (see https://github.com/10gen/mongo/pull/49667 and plan stability test).
What is interesting is that as a result of the change, we started choosing the optimal P-PS-S-N-L-O order, but a suboptimal join algorithm choice.
- is related to
-
SERVER-122314 Fix collection number leaf pages calculation to use on disk size
-
- Closed
-
- related to
-
SERVER-122612 Investigate plan quality/stability for TPC-H Q9 on SF 1
-
- Closed
-