Planning counters in pg_stat_statements

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Subject: Planning counters in pg_stat_statements
Date: 2017-11-07 05:10:45
Message-ID: CAEepm=0e59Y_6Q_YXYCTHZkqOc6H2pJ54C_Xe=VFu50Aqqp_sA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Attachment Content-Type Size
pg-stat-statements-planning-v1.patch application/octet-stream 18.9 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tsunakawa, Takayuki 2017-11-07 05:39:06 Re: Planning counters in pg_stat_statements
Previous Message Michael Paquier 2017-11-07 04:30:09 Re: LDAP URI decoding bugs