eG Monitoring
 

Measures reported by PgDeadLocksTest

A database deadlock is a situation in which two or more transactions are waiting for one another to give up locks. Because both transactions are waiting for a resource to become available, neither ever release the locks it holds.A deadlock causes one transaction to be aborted and the transaction must be restarted by the database server. This inturn causes more severe damage. f a deadlock occurs very often, it severely affects the performance of the database server. To avoid such critical situations, administrators need to constantly keep a vigil on the count of deadlocks and waiting time. The PostgreSQL Deadlocks Test helps administrators in this regard!

This test reports the number of deadlocks that occured and also the maximum waiting time, which helps administrators to detect and resolve the bottleneck condition before it affects the performance of the server.

Outputs of the test: One set of results for the target PostgreSQL server being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
NumberOfDeadlocks Indicates the number of deadlocks occurred in the target database Server. Number

A deadlock may arise due to various situations including bad design of queries and deficient coding practices. A deadlock is a situation where both/all the lock requestors are in a mutual or a multi-way tie. Any deadlocks are detrimental to database application performance.

The detailed diagnosis of this measure shows that information about the Database name, User name, Client host name, Client Port, Query start, Waiting duration (in seconds), State message, and Query text.
MaxDuration Indicates the maximum duration of the deadlock. Seconds

A low value is desired for this measure.