Re: pg_stat_statements and planning time

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Fujii Masao <masao.fujii@gmail.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2012-03-08T13:09:54Z

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 →

Allow pg_stat_statements to track planning statistics.
- 17e03282241c 13.0 landed

On Wed, Mar 7, 2012 at 9:59 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> I'd like to have the planning time in a number of other places as
>> well, such as EXPLAIN, and maybe statistics views.
>
> +1 for EXPLAIN. But which statistics views are in your mind?

I don't know.  I'm not sure if it's interesting to be able to count
planning time vs. execution time on a server-wide basis, or even a
per-database basis, but it seems like it might be, if we can do it
cheaply.  Then again, considering that gettimeofday is kinda
expensive, I suppose that would have to be optional if we were to have
it at all.  Just thinking out loud, mostly.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company