| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Wood <hexexpert(at)comcast(dot)net> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Wait profiling |
| Date: | 2020-07-10 20:37:13 |
| Message-ID: | 20200710203713.GA2569@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Jul-10, Daniel Wood wrote:
> After nearly 5 years does something like the following yet exist?
> https://www.postgresql.org/message-id/559D4729.9080704@postgrespro.ru
Yes, we have pg_stat_activity.wait_events which implement pretty much
what Ildus describes there.
> 1) An option to "explain" to produce a wait events profile.
> postgres=# explain (analyze, waitprofile) update pgbench_accounts set bid=bid+1 where aid < 2000000;
> ...
> Execution time: 23111.231 ms
There's an out-of-core extension, search for pg_wait_sampling. I
haven't tested it yet ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hsu, John | 2020-07-10 20:44:30 | Physical slot restart_lsn advances incorrectly requiring restore from archive |
| Previous Message | Michail Nikolaev | 2020-07-10 20:25:15 | Re: [PATCH] Btree BackwardScan race condition on Standby during VACUUM |