db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nirmal Fernando <nirmal070...@gmail.com>
Subject Re: [jira] Commented: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics
Date Thu, 25 Mar 2010 17:21:12 GMT
Thanks Bryan I will look in to those !!



On Thu, Mar 25, 2010 at 7:47 PM, Bryan Pendleton (JIRA) <jira@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849708#action_12849708]
>
> Bryan Pendleton commented on DERBY-4587:
> ----------------------------------------
>
> There is some information in the Derby wiki:
> http://wiki.apache.org/db-derby/LanguageSystem
>
> There is also lots of good information in the Derby docs, particularly
> here:
> http://db.apache.org/derby/docs/10.5/tuning/ctunoptimz39739.html
>
> All of these documents can always be improved, so it would be great if you
> can improve and expand on these sections as you study Derby. You can
> edit the wiki directly; you can submit doc patches for improvement just
> as you would code patches. Thanks!
>
> > 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.
>
>


-- 
Best Regards,
Nirmal

C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.

Mime
View raw message