Re: How to clock the time spent for query parsing and planning?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Igor <ischtein(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: How to clock the time spent for query parsing and planning?
Date: 2011-12-31 07:49:37
Message-ID: CAFj8pRB6tmQY+S_A3g+MZJZofvqea6EvpMHGMDrntLf4ashZOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

2011/12/31 Igor <ischtein(at)gmail(dot)com>:
> Hi Pavel,
>
> Thanks for your reply.
>
> My understanding is that Explain provides measurements of query run time but does not include or specifies the timing for  planning and for running optimization algorithms.

the a result of explain is visualisation of execution plan - so all
necessary steps (parsing, analysing, optimization) was processed. So
time of EXPLAIN is time that you looking. Other similar value should
by time of PREPARE statement.

Regards

Pavel

>
> Pls let me know if my understanding is not  correct. In that case, how do I find out how much of query time is spent to prepare the query and how much time is spent executing it.
>
> Thanks,
> James
>
> On Dec 27, 2011, at 1:38 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>> Hello
>>
>> 2011/12/23 Igor Schtein <ischtein(at)gmail(dot)com>:
>>> I'd like to find some measurements/figures of query preparation and planning
>>> time to justify the use of prepared statements and stored procedures.
>>> I know that complex queries have larger preparation time. Though, is it
>>> possible to explicitly measure the time the optimizer spends parsing and
>>> planning for query execution?
>>
>> You can use time for EXPLAIN statement
>>
>> Regards
>>
>> Pavel Stehule
>>
>>>
>>> Thank you,
>>> James

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jay Levitt 2012-01-01 18:59:25 Cost estimate vs. actual - do I care?
Previous Message Igor 2011-12-31 00:59:57 Re: How to clock the time spent for query parsing and planning?