Re: pg_stat_statements and planning time

Fujii Masao <masao.fujii@gmail.com>

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

To: Simon Riggs <simon@2ndquadrant.com>

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

Date: 2012-03-07T12:18: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:00 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Wed, Mar 7, 2012 at 11:45 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
>
>> Attached patch extends pg_stat_statements so that it reports the
>> planning time. Thought?
>
> If we successfully aggregate SQL in the current patch then this might
> be useful as well. Until we do that it's not much use.

You mean pg_stat_statements normalization patch? Yes, if it will be applied,
this patch would be more useful. But without the normalization patch, this patch
would be useful for a user who use the extended protocol but not plan cache
mechanism, I think.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center