Thanks Stamatis.... I will look into that and get back to you.... On Sat, 1 Dec 2018, 10:28 am Stamatis Zampetakis <zabe...@gmail.com wrote:
> Hi Lekshmi, > > I don't think that you can obtain this information easily. The current > implementation of explain does not seem to provide this information. > If you are willing to dig in a bit into the code you might find useful the > following entry points regarding the timing of queries: CalciteTimingTracer > < > https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/util/trace/CalciteTimingTracer.java > > > , CalciteTrace > < > https://github.com/apache/calcite/blob/439ca73b8a335213b5f2764514b14e17c9d3c216/core/src/main/java/org/apache/calcite/util/trace/CalciteTrace.java#L103 > > > . > > Best, > Stamatis > > Στις Παρ, 30 Νοε 2018 στις 11:33 μ.μ., ο/η Lekshmi <lekshmib...@gmail.com> > έγραψε: > > > Hi, > > I was comparing the performance of PostgreSQL and Calcite. I can > collect > > the planning and execution time from PostgreSQL using "explain analyze" > but > > from calcite I didnt get all the information using "explain all > > attributes". I would like to know how can we collect the execution time > and > > planning time of a query from calcite..It would be great, if anyone help > > me.. > > > > Thanks and Regards > > > > Lekshmi B.G > > Email: lekshmib...@gmail.com > > >
