[
https://issues.apache.org/jira/browse/DERBY-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461237#comment-13461237
]
Bryan Pendleton commented on DERBY-837:
---------------------------------------
Having this in place would be a very helpful tool for working on problems like
DERBY-5933,
where it isn't immediately clear why the optimizer is choosing an invalid query
plan, and being
able to trace its execution would be quite valuable.
Mamta, I see that in the linked email message in the description, you mentioned
that you had
done a partial implementation of this feature. Do you still have that
implementation available?
> Enable optimizer trace in Derby
> -------------------------------
>
> Key: DERBY-837
> URL: https://issues.apache.org/jira/browse/DERBY-837
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.2.1.6
> Reporter: Mamta A. Satoor
>
> Derby engine has code to produce trace for optimization phase ie various
> plans considered by the optimizer for a query. This trace however does not
> get produced because there is no way to turn the trace on. When someone does
> work on providing a way to enable the optimizer trace, we will also need to
> decide in what format this trace should be presented. Further information on
> this issue can be found at
> http://article.gmane.org/gmane.comp.apache.db.derby.devel/12288
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
