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 | CAM3SWZQ8yp4Xaey__kgdXger6PXwGPD1FLpfv2qj9evqyvyq6g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Add min and max execute statement time in pg_stat_statement (Jeff Janes <jeff.janes@gmail.com>) |
| Ответы |
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 4:14 PM, Jeff Janes <jeff.janes@gmail.com> wrote: > The last bucket would be limited to 8ms < x <= 16 ms. If you find something >> 16ms, then you have to rescale *before* you increment any of the buckets. > Once you do, there is now room to hold it. How is that laid out in shared memory? If the answer is an array of 32 int64s, one per bucket, -1 from me to this proposal. A huge advantage of pg_stat_statements today is that the overhead is actually fairly modest. I really want to preserve that property. -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: