You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DTrace probes for lock-wait-start and lock-wait-done provide tags that can be used to identify the type of locked object (a table, a relation, a transaction) and the mode of lock wanted (various types of shared or exclusive locks). There's some detail in the documentation for locking overall and the pg_locks view. The probes also include tags that can contain the database, relation, or transaction id, depending on what's being locked.
We've found workloads where queries spend most of their time waiting on locks. There are lot of ways we might like to slice the data we can get:
per-transaction basis: lock wait events and total time blocked on locks (could be added to pgtxslower)
per-lock basis: lock wait events and total time blocked on each different lock
overall distribution of lock wait time
It would be very valuable just to be able to print out the lock wait events in a human-readable form (i.e., mapping the locked object and the lock mode to string values).
The text was updated successfully, but these errors were encountered:
The DTrace probes for lock-wait-start and lock-wait-done provide tags that can be used to identify the type of locked object (a table, a relation, a transaction) and the mode of lock wanted (various types of shared or exclusive locks). There's some detail in the documentation for locking overall and the
pg_locks
view. The probes also include tags that can contain the database, relation, or transaction id, depending on what's being locked.We've found workloads where queries spend most of their time waiting on locks. There are lot of ways we might like to slice the data we can get:
pgtxslower
)It would be very valuable just to be able to print out the lock wait events in a human-readable form (i.e., mapping the locked object and the lock mode to string values).
The text was updated successfully, but these errors were encountered: