[SERVER-8208] support explain() without actually executing the query Created: 17/Jan/13 Updated: 10/Dec/14 Resolved: 14/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anh H. Trinh | Assignee: | David Storch |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When you have a bad performing query, it is helpful to be able to see the query plan without running the query itself. Execution of a bad query may take hours (or god knows how long), so the explain() command is of no help when it is needed the most. |
| Comments |
| Comment by David Storch [ 14/Oct/14 ] |
|
This feature is supported by the new explain format introduced in the 2.7 development branch. Changes to explain for the 2.7 development series are being tracked by |