From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Measuring execution time |
Date: | 2010-08-11 02:42:40 |
Message-ID: | 4C620E20.4060608@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 10/08/10 19:46, vamsi krishna wrote:
> Hello all
> I want to measure the execution time spent running an SQL select query
> after the plan generation.
> So precisely I want to put my start timer before createQueryDesc() or
> ExecutorStart() and end timer after freeQueryDesc() or ExecutorEnd().
> Right now I did so in "spi.c", "explain.c", "pquery.c" but they are
> not the default execution cases. Can someone tell me which file holds
> the default call to ExecutorStart(), because I also want to see the
> select query result unlike in the case of "explain" ?
>
See ProcessQuery in src/backend/tcop/query.c
Cheers
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-11 02:55:21 | Re: BUG #5611: SQL Function STABLE promoting to VOLATILE |
Previous Message | Brian Ceccarelli | 2010-08-10 20:30:50 | BUG #5611: SQL Function STABLE promoting to VOLATILE |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2010-08-11 02:55:35 | Re: Measuring execution time |
Previous Message | Tom Lane | 2010-08-11 00:19:27 | Re: Surprising dead_tuple_count from pgstattuple |