| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Arne Scheffer <scheffa(at)uni-muenster(dot)de> |
| Cc: | Arne Scheffer <arne(dot)scheffer(at)uni-muenster(dot)de>, 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:32:57 |
| Message-ID: | 54BFD4B9.9050707@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
But I will add a note to the documentation, that seems reasonable.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arne Scheffer | 2015-01-21 16:58:23 | Re: Add min and max execute statement time in pg_stat_statement |
| Previous Message | Adam Brightwell | 2015-01-21 16:27:31 | Re: Additional role attributes && superuser review |