Hi,
When examining the duration of locks, we often do join on pg_locks
and pg_stat_activity and use columns such as query_start or
state_change.
However, since these columns are the moment when queries have
started or their state has changed, we cannot get the exact lock
duration in this way.
So I'm now thinking about adding a new column in pg_locks which
keeps the time at which locks started waiting.
One problem with this idea would be the performance impact of
calling gettimeofday repeatedly.
To avoid it, I reused the result of the gettimeofday which was
called for deadlock_timeout timer start as suggested in the
previous discussion[1].
Attached a patch.
BTW in this patch, for fast path locks, wait_start is set to
zero because it seems the lock will not be waited for.
If my understanding is wrong, I would appreciate it if
someone could point out.
Any thoughts?
[1]
https://www.postgresql.org/message-id/28804.1407907184%40sss.pgh.pa.us
Regards,
--
Atsushi Torikoshi
NTT DATA CORPORATION
