Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- auto-reverted
- query-perf-q4

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Linked BF Score:
154
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

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

Assignee:: Zixuan Zhuang
Reporter:: Ian Boros
Participants:: Githook User, Ian Boros, Zixuan Zhuang
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Nov 15 2023 07:49:37 PM UTC
Updated:: Mar 18 2024 05:36:23 PM UTC
Resolved:: Jan 17 2024 10:52:21 PM UTC
Confidence Status Last Update:: 16/Jan/24 6:07 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates