| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp>, Haribabu kommi <haribabu(dot)kommi(at)huawei(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improvement of pg_stat_statement usage about buffer hit ratio |
| Date: | 2013-11-18 18:56:56 |
| Message-ID: | CAM3SWZS9470xGoF=wbqSGsmT55A9AniWBU9o75QrXoA8589-Fg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 18, 2013 at 10:49 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> The same idea was proposed before but not committed because
> Itagaki thought that pg_stat_statements view should report only raw values.
> Please read the following thread. I have the same feeling with him.
> Anyway we should listen to more opinions from other people, though.
> http://www.postgresql.org/message-id/20091222172719.8B86.52131E4D@oss.ntt.co.jp
+1 from me. I think that a higher level tool needs to be built on
pg_stat_statements to make things easy for those that want a slick,
pre-packaged solution. As I said on the min/max thread, if we're not
doing enough to help people who would like to build such a tool, we
should discuss how we can do better.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2013-11-18 18:58:26 | Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 |
| Previous Message | Fujii Masao | 2013-11-18 18:49:30 | Re: Improvement of pg_stat_statement usage about buffer hit ratio |