db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics
Date Sun, 28 Mar 2010 18:46:27 GMT

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

Bryan Pendleton commented on DERBY-4587:
----------------------------------------

I think these sound like great ideas. I think it would be good to work on this
incrementally, starting with a fairly simple stylesheet and then improving it.

I think this approach could be prototyped to show its feasibility, by
doing something along the lines of:

1) Capture a fairly simple query plan, for example capture the query plan for:

   select from cities where city_name = 'New Orleans';

2) By hand, convert that captured query plan to an XML format using your text editor

3) Develop a simple XSLT stylesheet which can display some of the basic query plan information

4) Attach the original query plan, the XML formatted plan, and the stylesheet, so
    that the community can see a sample of your ideas.


> Add tools for improved analysis and understanding of query plans and execution statistics
> -----------------------------------------------------------------------------------------
>
>                 Key: DERBY-4587
>                 URL: https://issues.apache.org/jira/browse/DERBY-4587
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, Tools
>            Reporter: Bryan Pendleton
>            Assignee: Bryan Pendleton
>         Attachments: PostgreSQL license.jpg
>
>
> I think it would be great to see some work in the area of tools for helping
> with the analysis of complex query execution. Quite frequently, users of
> Derby have trouble comprehending (a) how their query is being translated
> into a query plan by the optimizer, and (b) what the execution-time resource
> usage of the various parts of the query is.
> There are low-level features in Derby which capture this information and
> record it, such as logQueryPlan, and the XPLAIN tables, but there is a lot
> of opportunity for designing higher-level tools which can process the query
> plan and execution statistics information and present it in a more
> comprehensible fashion. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message