Re: Add min and max execute statement time in pg_stat_statement

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Petr Jelinek <petr(at)2ndquadrant(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Arne Scheffer <arne(dot)scheffer(at)uni-muenster(dot)de>, David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add min and max execute statement time in pg_stat_statement
Date: 2015-02-17 00:57:49
Message-ID: CAM3SWZTbE5BqQDJsuGns9QVTK-q7R2oOVjVOjTHXN7w4ZM0VGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 16, 2015 at 4:44 PM, Petr Jelinek <petr(at)2ndquadrant(dot)com> wrote:
> We definitely want this feature, I wished to have this info many times.

I would still like to see a benchmark.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-02-17 01:27:55 We do not need pg_promote_v4_to_v6_addr/mask
Previous Message Petr Jelinek 2015-02-17 00:44:48 Re: Add min and max execute statement time in pg_stat_statement