Re: Measuring execution time
От | Mark Kirkwood |
---|---|
Тема | Re: Measuring execution time |
Дата | |
Msg-id | 4C621127.8010300@catalyst.net.nz обсуждение исходный текст |
Ответ на | Re: Measuring execution time (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>) |
Список | pgsql-hackers |
On 11/08/10 14:42, Mark Kirkwood wrote:
Doh - sorry, I see you have that guy! Have a look at exec_simple_query in src/backend/tcop/postgres.c, by the time pg_plan_queries returns you have finished planning. The call to CreateQueryDesc is going to be from PortalStart in that case. Hopefully this will get you started (you may need to look at exec_*_message functions too).
Mark
On 10/08/10 19:46, vamsi krishna wrote:Hello allI 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
Doh - sorry, I see you have that guy! Have a look at exec_simple_query in src/backend/tcop/postgres.c, by the time pg_plan_queries returns you have finished planning. The call to CreateQueryDesc is going to be from PortalStart in that case. Hopefully this will get you started (you may need to look at exec_*_message functions too).
Mark
В списке pgsql-hackers по дате отправления: