-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
(copied to CRM)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Presently if an operation terminates unsuccessfully (eg from exceeding max time). Entries in the slow query log lack some of the runtime metrics when this happens. This limits the value of the entries for diagnostic purposes.
We should be able to capture some additional information to improve the diagnostic value entries in such situations. In particular let's capture planSummary earlier in the execution process if possible so that it is available even in the case of early termination.
- is related to
-
SERVER-49808 Report execution stats for logging/profiling in PlanExecutorPipeline::getStats()
-
- Backlog
-
-
SERVER-93786 Extend tassert diagnostic logging to include explain information
-
- Closed
-