Details
-
New Feature
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
Query
Description
It would be very useful IMHO, if dbCurrentOp could show the index currently in use for a (possibly long running) query. This would make it so much easier to spot bad optimizer decisions (which there are plentiful of in 2.6, unfortunately) where a hint should be added to the query.
Attachments
Issue Links
- duplicates
-
SERVER-23259 Report planSummary in per-operation diagnostic log message and profiler for all relevant ops/commands
-
- Closed
-
- is related to
-
SERVER-17862 Unify stats reporting for log/profiler across CRUD operations
-
- Closed
-