Re: Add min and max execute statement time in pg_stat_statement
От | Peter Geoghegan |
---|---|
Тема | Re: Add min and max execute statement time in pg_stat_statement |
Дата | |
Msg-id | CAM3SWZQYJMGHAOAR-6yBBndqwbJveY3ACJFRN1TEs8zR_Ah3+A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Add min and max execute statement time in pg_stat_statement (Gavin Flower <GavinFlower@archidevsys.co.nz>) |
Ответы |
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 Wed, Oct 23, 2013 at 2:57 PM, Gavin Flower <GavinFlower@archidevsys.co.nz> wrote: > Looks definitely bimodal in the log version, very clear! > > Yes, I feel that having a 32 log binary binned histogram (as Alvaro Herrera > suggested) would be very useful. I'm having a hard time imagining how you'd actually implement that. For example, this: https://wiki.postgresql.org/wiki/Aggregate_Histogram requires that a "limit" be specified ahead of time. Is there a principled way to increase or decrease this kind of limit over time, and have the new buckets contents "spill into each other"? -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: