For users with index filters, the performance of the application can rely on the index filters being set correctly. Currently, setting an index filter using the planCacheSetFilter command will only be logged if the slowms threshold is exceeded or if the logLevel is greater than 0. Logging these events would be useful both as a sanity check that the correct filter was applied and for postmortem analysis in the case that queries using index filters experience plan selection problems. Setting an index filter should be a rare event and therefore should not have any significant impact on the verbosity of logLevel 0 log files.
Add log statement at default log level for when an index filter is set or cleared successfully
- Votes:
-
0 Vote for this issue
- Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: