[SERVER-18466] Log when and why a query shape begins to use a different plan Created: 13/May/15  Updated: 25/Jun/15  Resolved: 20/May/15

Status: Closed
Project: Core Server
Component/s: Diagnostics, Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Charlie Page Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-13220 Add and expose statistics to new quer... Backlog
Related
is related to SERVER-18013 Expose more execution stats from plan... Closed
is related to SERVER-18468 Include query planning details on que... Closed
Participants:

 Description   

Currently, if a plan occasionally flips flops to a less optimal query (or a bug occurs) it can be extremely challenging (or impossible), to catch the plan cache in the bad state.

Setting the QLOG on for all queries isn't reasonable as that generates too much output for high use systems.

Having an option to only output the QLOG if the plan changes so that the reason for change can be recorded automatically enable the quick diagnosis of these cases.



 Comments   
Comment by J Rassi [ 20/May/15 ]

Closing this as a dup of SERVER-13220, which will improve the drill-down process for query plan selection issues.

Generated at Thu Feb 08 03:47:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.