PGXC_LOCK_CONFLICTS
PGXC_LOCK_CONFLICTS displays information about conflicting locks in the cluster.
When a lock is waiting for another lock or another lock is waiting for this one, a lock conflict occurs.
Currently, PGXC_LOCK_CONFLICTS collects only information about locks whose locktype is relation, partition, page, tuple, or transactionid.
Column |
Type |
Description |
---|---|---|
locktype |
Text |
Type of the locked object |
nodename |
Name |
Name of the node where the locked object resides |
dbname |
Name |
Name of the database where the locked object resides. The value is NULL if the locked object is a transaction. |
nspname |
Name |
Name of the namespace of the locked object |
relname |
Name |
Name of the relation targeted by the lock. The value is NULL if the object is not a relation or part of a relation. |
partname |
Name |
Name of the partition targeted by the lock. The value is NULL if the locked object is not a partition. |
page |
Integer |
Number of the page targeted by the lock. The value is NULL if the locked object is neither a page nor a tuple. |
tuple |
Smallint |
Number of the tuple targeted by the lock. The value is NULL if the locked object is not a tuple. |
transactionid |
Xid |
ID of the transaction targeted by the lock. The value is NULL if the locked object is not a transaction. |
username |
Name |
Name of the user who applies for the lock |
gxid |
Xid |
ID of the transaction that applies for the lock |
xactstart |
Timestamp with time zone |
Start time of the transaction that applies for the lock |
queryid |
Bigint |
Latest query ID of the thread that applies for the lock |
query |
Text |
Latest query statement of the thread that applies for the lock |
pid |
Bigint |
ID of the thread that applies for the lock |
mode |
Text |
Lock mode |
granted |
Boolean |
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.