On Thu, Mar 8, 2012 at 12:39 AM, Robert Haas <robertmh...@gmail.com> wrote: > On Wed, Mar 7, 2012 at 6:45 AM, Fujii Masao <masao.fu...@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.
Yes. I will add this to the next commitfest. And, in the patch, I changed pg_stat_statements--1.1.sql, but, for 9.3 I will have to create 1.2.sql instead. > 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? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
