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: PlanExporter and invoking TimingStatistics
Date Tue, 18 Jan 2011 13:20:06 GMT
Hi,

On Tue, Jan 18, 2011 at 4:07 PM, Knut Anders Hatlen
<knut.hatlen@oracle.com> wrote:
>
> Nirmal Fernando <nirmal070125@gmail.com> writes:
>
> > Hi,
> >
> > Current PlanExporter is not mentioning the fact that an user need to
> > invoke "TimingStatistics" when he executing the query to be analyzed
> > (see section 4 in
> > http://db.apache.org/derby/docs/10.7/tools/rtoolsplanexpexamples.html).
> > But without invoking that "SYSXPLAIN_RESULTSET_TIMINGS" table will not
> > be logged.
> >
> > So, I like to get your opinion on this. Is it better to ask user to
> > invoke timing statistics as well or are we going to avoid adding
> > details of "TIMINGS" tables in the query plan?
>
> Would it be possible to add timing info only if the user has enabled
> timing? If no timing info is available, the tool could continue to
> produce reports without timing, like it does today. We could document
> SYSCS_SET_STATISTICS_TIMING as an optional step that users must perform
> if they want information about timing in the plan.

This approach may possible, but need to check after writing the db queries.

Thanks Knut!!

>
> --
> Knut Anders



--
Best Regards,
Nirmal

C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.
Blog: http://nirmalfdo.blogspot.com/

Mime
View raw message