Re: Improvement of pg_stat_statement usage about buffer hit ratio - Mailing list pgsql-hackers

From KONDO Mitsumasa
Subject Re: Improvement of pg_stat_statement usage about buffer hit ratio
Date
Msg-id 5289FBCB.5000601@lab.ntt.co.jp
Whole thread Raw
In response to Re: Improvement of pg_stat_statement usage about buffer hit ratio  (Haribabu kommi <haribabu.kommi@huawei.com>)
Responses Re: Improvement of pg_stat_statement usage about buffer hit ratio  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
(2013/11/18 20:16), Haribabu kommi wrote:
> On 18 October 2013 13:35 KONDO Mitsumasa wrote:
>> This patch conflicts pg_stat_statement_min_max_exectime patch which I
>> submitted, and pg_stat_statement_min_max_exectime patch also adds new
>> columns which are min_time and max_time. So I'd like to change it in
>> this opportunity.
>
> This patch adds another column "shared_blks_hit_percent" to pg_stat_statements view
> Which is very beneficial to the user to know how much percentage of blks are hit.
>
> All changes are fine and working as described. Marked as ready for committer.
Thank you for your reviewing!

However, I'd like to add average time in each statement, too. Attached patch is
my latest one. Adding shared_blks_hit_percent and ave_time. This is the adding
main code.
> +         total_time / calls::float AS avg_time,

If this patch and min/max and stddev patch will be commited, we can see more
detail and simple information in pg_stat_statements, by light-weight coding.

Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: Haribabu kommi
Date:
Subject: Re: Improvement of pg_stat_statement usage about buffer hit ratio
Next
From: Andres Freund
Date:
Subject: Re: Sequence Access Method WIP