-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: 2.5.4
-
Component/s: Diagnostics, Querying
-
Labels:None
db.setProfilingLevel(0)
db.system.profile.drop()
db.bar.drop();
db.bar.insert( { "x" : 7, "r" : 0.999768219422549 } )
db.bar.insert( { "x" : 92, "r" : 0.9881451367400587 } )
db.bar.insert( { "x" : 45, "r" : 0.9833264029584825 } )
// no indexes other than { _id: 1 }
db.setProfilingLevel(2)
db.bar.find().sort( { r: -1 } )
db.system.profile.find().sort( {$natural: 1} ).limit(1).pretty();
In 2.4.x we see a document that has the scanAndOrder field which doesn't appear in 2.5.5-pre.
Previously scanAndOrder only appeared when true, which is itself a bit odd.
- depends on
-
SERVER-10566 performance pass: idhack, findingStartCursor, other profiling and opt
-
- Closed
-
- is depended on by
-
-
- Closed
-