-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:
In 2.4 and 2.6, nscanned was calculated as every matching key returned by the index scan plus any out-of-range key which was examined before seeking to the start of the next range. The same holds in 3.0 for the keysExamined statistic. However, this code always had a strange exception in which it did not count the last out-of-range key examined.
In the release notes we should document that, as of 3.2, the final out-of-range key (i.e. the "end" key) is counted towards keysExamined.
See SERVER-16381 for details.
- documents
-
SERVER-16381 Index scans don't include the final "end" check within nscanned/keysExamined
- Closed