Re: proposal: simple query profile and tracing API
От | legrand legrand |
---|---|
Тема | Re: proposal: simple query profile and tracing API |
Дата | |
Msg-id | 1542200752538-0.post@n3.nabble.com обсуждение исходный текст |
Ответ на | Re: proposal: simple query profile and tracing API (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: proposal: simple query profile and tracing API
|
Список | pgsql-hackers |
Pavel Stehule wrote > út 13. 11. 2018 v 20:38 odesílatel Tomas Vondra < > tomas.vondra@ >> napsal: > > My idea is very simple. > > 1. continual collect of data - planning start, execution start, waiting > start, waiting end, query end > > 2. run a some callback function after query is finished. Collected data > will be passed there. > > I think so anybody can do some different with these data. Sometimes only > sum can be ok, sometimes you need to increment some sorted counts, > sometimes you need to store these data for median or percentil > calculation. > > I think so it can be very simple and fast, because you should to work with > just one metrics vector. the same idea was already proposed for planning time in pg_stat_statements by Thomas https://www.postgresql-archive.org/Planning-counters-in-pg-stat-statements-tt5990933.html#a6002416 Regards PAscal -- Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
В списке pgsql-hackers по дате отправления: