Horton

Re: pg_stat_statements and planning time

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-03-07T15:39:40Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow pg_stat_statements to track planning statistics.

On Wed, Mar 7, 2012 at 6:45 AM, Fujii Masao <masao.fujii@gmail.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