| From: | Arne Scheffer <arne(dot)scheffer(at)uni-muenster(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add min and max execute statement time in pg_stat_statement |
| Date: | 2015-01-21 16:58:23 |
| Message-ID: | permail-20150121165823fe5316b6000001cc-scheffa@message-id.uni-muenster.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan schrieb am 2015-01-21:
> On 01/21/2015 11:21 AM, Arne Scheffer wrote:
> >Why is it a bad thing to call the column "stddev_samp" analog to the
> >aggregate function or make a note in the documentation, that the
> >sample stddev is used to compute the solution?
> I think you are making a mountain out of a molehill, frankly. These
> stats are not intended as anything other than a pretty indication of
> the
> shape, to see if they are significantly influenced by outliers. For
> any
> significantly large sample size the difference will be negligible.
You're right, I maybe exaggerated the statistics part a bit.
I wanted to help, because the patch is of interest for us.
I will try to keep focus in the future.
> But I will add a note to the documentation, that seems reasonable.
*happy*
Thx
Arne
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-01-21 17:47:44 | Re: moving from contrib to bin |
| Previous Message | Andrew Dunstan | 2015-01-21 16:32:57 | Re: Add min and max execute statement time in pg_stat_statement |