[HACKERS] Planning counters in pg_stat_statements - Mailing list pgsql-hackers

From Thomas Munro
Subject [HACKERS] Planning counters in pg_stat_statements
Date
Msg-id CAEepm=0e59Y_6Q_YXYCTHZkqOc6H2pJ54C_Xe=VFu50Aqqp_sA@mail.gmail.com
Whole thread Raw
Responses Re: [HACKERS] Planning counters in pg_stat_statements  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Re: [HACKERS] Planning counters in pg_stat_statements  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
Hi hackers,

I have often wanted $SUBJECT and was happy to find that Fujii-san had
posted a patch five years ago[1].  The reception then seemed positive.
So here is a refurbished and (hopefully) improved version of his patch
with a new column for the replan count.  Thoughts?

Example output:

             query              | plans | plan_time | calls | total_time
--------------------------------+-------+-----------+-------+------------
 prepare x as select $1         |     1 |     0.026 |    12 |       0.06
 select substr(query, $1, $2),  |    11 |     1.427 |    11 |      3.565
 prepare y as select * from foo |     2 |     7.336 |     5 |      0.331

I agree with the sentiment on the old thread that
{total,min,max,mean,stddev}_time now seem badly named, but adding
"execution" makes them so long...  Thoughts?

[1] https://www.postgresql.org/message-id/CAHGQGwFx_%3DDO-Gu-MfPW3VQ4qC7TfVdH2zHmvZfrGv6fQ3D-Tw%40mail.gmail.com

-- 
Thomas Munro
http://www.enterprisedb.com

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] LDAP URI decoding bugs
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: [HACKERS] Planning counters in pg_stat_statements