| From: | Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [Proposal] Add accumulated statistics for wait event |
| Date: | 2018-07-23 08:41:38 |
| Message-ID: | 40e27596-90dc-1c24-9ad6-bebd3e7a31fa@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
that will be a great feature.
On 23.07.2018 10:53, Michael Paquier wrote:
> I have comments about your patch. First, I don't think that you need to
> count precisely the number of wait events triggered as usually when it
> comes to analyzing a workload's bottleneck what counts is a periodic
> *sampling* of events
If I get it right, this patch is not about sampling. It gathers
cumulative statistics, which is regrettably missing in PostgreSQL.
That's why it should not only count exact number of wait events, but
also min time and stddev would be helpful (as in pg_stat_statements).
--
Egor Rogov
Postgres Professional http://www.postgrespro.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-07-23 08:45:11 | Re: [bug fix] Produce a crash dump before main() on Windows |
| Previous Message | Ashutosh Bapat | 2018-07-23 08:38:44 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |