On Thu, Mar 24, 2016 at 7:28 AM, Alexander Korotkov <a.korot...@postgrespro.ru> wrote: > Since, patch for exposing current wait event information in PGPROC was > committed, it becomes possible to collect wait event statistics using > sampling. Despite I'm not fan of this approach, it is still useful and > definitely better than nothing. > In PostgresPro, we actually already had it. Now, it's too late to include > something new to 9.6. This is why I've rework it and publish at github as > an extension for 9.6: https://github.com/postgrespro/pg_wait_sampling/ > Hopefully, it could be considered as contrib for 9.7.
Spiffy. That was fast. I think the sampling approach is going to be best on very large systems under heavy load; I suspect counting every event is going to be too expensive - especially once we add more events for things like block read and client wait. It is quite possible that we can do other things when tracing individual sessions or in scenarios where some performance degradation is OK. But I like the idea of doing the sampling thing first - I think that will be very useful. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
