Re: Add min and max execute statement time in pg_stat_statement

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add min and max execute statement time in pg_stat_statement
Date: 2014-01-29 20:07:47
Message-ID: 52E95F93.70407@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/29/2014 11:54 AM, Robert Haas wrote:
> I agree. I find it somewhat unlikely that pg_stat_statements is
> fragile enough that these few extra counters are going to make much of
> a difference. At the same time, I find min and max a dubious value
> proposition. It seems highly likely to me that stddev will pay its
> way, but I'm much less certain about the others.

What I really want is percentiles, but I'm pretty sure we already shot
that down. ;-)

I could use min/max -- think of performance test runs. However, I agree
that they're less valuable than stddev.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2014-01-29 20:11:38 Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication
Previous Message Robert Haas 2014-01-29 20:01:01 Re: Planning time in explain/explain analyze