Re: Wait profiling
От | Julien Rouhaud |
---|---|
Тема | Re: Wait profiling |
Дата | |
Msg-id | CAOBaU_bvFXfH0DETUAAGUzStYH=kByNkjDtk-9av5tPWr=Wv-A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Wait profiling (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Список | pgsql-hackers |
On Fri, Jul 10, 2020 at 10:37 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > 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 ... I use it, and I know multiple people that are also using it (or about to, it's currently being packaged) in production. It's working quite well and is compatible with pg_stat_statements' queryid. You can see some examples of dashboards that can be built on top of this extension at https://powa.readthedocs.io/en/latest/components/stats_extensions/pg_wait_sampling.html.
В списке pgsql-hackers по дате отправления: