Re: Add min and max execute statement time in pg_stat_statement
| От | Andrew Dunstan |
|---|---|
| Тема | Re: Add min and max execute statement time in pg_stat_statement |
| Дата | |
| Msg-id | 54BFD4B9.9050707@dunslane.net обсуждение исходный текст |
| Ответ на | Re: Add min and max execute statement time in pg_stat_statement (Arne Scheffer <scheffa@uni-muenster.de>) |
| Ответы |
Re: Add min and max execute statement time in
pg_stat_statement
Re: Add min and max execute statement time in pg_stat_statement |
| Список | 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
В списке pgsql-hackers по дате отправления: