Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Query Execution
-
Fully Compatible
-
154
Description
When we make an index scan SBE plan with point bounds, we end up calling next() in the storage layer more than once, even though a unique index guarantees that there can only be one key. We should consider optimizing this.
Attachments
Issue Links
- is related to
-
SERVER-85577 Missing fields in KeyString cause incorrect point bound validation
-
- Closed
-
-
SERVER-85727 [v7.3] Revert "Ixscan plans on unique indexes needlessly call next() on storage cursor" in 7.3
-
- Closed
-