From 6eb9c5a5657d1fe77b55cc261450f3538d35a94d Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:19:15 +0200 Subject: Adding upstream version 13.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/monitoring-locks.html | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/src/sgml/html/monitoring-locks.html (limited to 'doc/src/sgml/html/monitoring-locks.html') diff --git a/doc/src/sgml/html/monitoring-locks.html b/doc/src/sgml/html/monitoring-locks.html new file mode 100644 index 0000000..b6c2bc8 --- /dev/null +++ b/doc/src/sgml/html/monitoring-locks.html @@ -0,0 +1,28 @@ + +27.3. Viewing Locks
27.3. Viewing Locks
Prev UpChapter 27. Monitoring Database ActivityHome Next

27.3. Viewing Locks

+ Another useful tool for monitoring database activity is the + pg_locks system table. It allows the + database administrator to view information about the outstanding + locks in the lock manager. For example, this capability can be used + to: + +

  • + View all the locks currently outstanding, all the locks on + relations in a particular database, all the locks on a + particular relation, or all the locks held by a particular + PostgreSQL session. +

  • + Determine the relation in the current database with the most + ungranted locks (which might be a source of contention among + database clients). +

  • + Determine the effect of lock contention on overall database + performance, as well as the extent to which contention varies + with overall database traffic. +

+ + Details of the pg_locks view appear in + Section 51.73. + For more information on locking and managing concurrency with + PostgreSQL, refer to Chapter 13. +

Prev Up Next
27.2. The Statistics Collector Home 27.4. Progress Reporting
\ No newline at end of file -- cgit v1.2.3