db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-837) Enable optimizer trace in Derby
Date Tue, 21 Oct 2014 21:31:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179147#comment-14179147

Myrna van Lunteren commented on DERBY-837:

We now have the pluggable optimizer tracing tool (see DERBY-6211). Can this issue be closed
as a duplicate?

> 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:
>            Reporter: Mamta A. Satoor
>              Labels: derby_triage10_11
>         Attachments: enableOptimizerTraceHacksvndiff.txt, enableOptimizerTraceHacksvnstat.txt
> 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 was sent by Atlassian JIRA

View raw message