Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0, v7.0
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

In ~~SERVER-92764~~ we extended tassert diagnostic printing to dump contents of CurOp/OpDebug.

We should consider logging plan explain (at "queryPlanner" verbosity level at the very least) as well, if it's safe to do so (that is, if we don't need to follow any synchronization protocol or read from disk).

is related to

SERVER-49808 Report execution stats for logging/profiling in PlanExecutorPipeline::getStats()

Backlog

SERVER-101049 Consider lint rule warning/enforcing no new invariant introduction in explain components

Backlog

related to

SERVER-100060 Capture planSummary in log when operation terminates unsuccessfully

Needs Scheduling

split to

SERVER-100720 Introduce basic unit tests for PlanExplainer

Closed

Assignee:: Hana Pearlman
Reporter:: Anton Korshunov
Participants:: Anton Korshunov, Githook User, Hana Pearlman
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Aug 20 2024 04:45:21 PM UTC
Updated:: Jul 29 2025 05:33:14 PM UTC
Resolved:: Feb 20 2025 01:58:11 PM UTC
Confidence Status Last Update:: 02/Jan/25 4:58 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates