From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_stat_statements and planning time |
Date: | 2012-03-07 15:39:40 |
Message-ID: | CA+TgmoY1HFaX9wqwMRKpsYJheYGzpY=7D2dEnz6R7MpZYOjNMg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 7, 2012 at 6:45 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> pg_stat_statements is basically very helpful to find out slow queries.
> But since it doesn't report the time spent in the planner, we cannot
> find out slow queries which take most time to do query planning, from
> pg_stat_statements. Is there any reason why pg_stat_statements doesn't
> collect the planning time?
>
> Attached patch extends pg_stat_statements so that it reports the
> planning time. Thought?
I think this is an interesting idea, but I think it's too late for 9.2.
I'd like to have the planning time in a number of other places as
well, such as EXPLAIN, and maybe statistics views.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2012-03-07 15:44:19 | Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) |
Previous Message | Tom Lane | 2012-03-07 15:28:38 | Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) |