Re: execution time and planning time from Calcite

Hi Stamatis, Thank you so much for your help and I appreciate your prompt response. I think, I mixed our conversation by bringing in the TPCH query stuff. So, coming to the tracing part, I was able to create the timing tracer using the classes *CalciteTimingTracer* and *CalciteTrace* and was

Re: execution time and planning time from Calcite

Hi Lekshmi, Basically, I think you just need to add some log information inside Prepare . Possibly it suffices to replace calls to timingTracer

Re: execution time and planning time from Calcite

Thanks Stamatis I will look into that and get back to you On Sat, 1 Dec 2018, 10:28 am Stamatis Zampetakis 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

Re: execution time and planning time from Calcite

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:

execution time and planning time from Calcite

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