-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional metric number of database locks #26317
Labels
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Sep 3, 2023
djaglowski
pushed a commit
that referenced
this issue
Sep 5, 2023
…26318) **Description:** Added new metric -- postgresql.database_locks -- the number of database locks . **Link to tracking Issue:** #26317 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> --------- Co-authored-by: Antoine Toulme <[email protected]>
I checked with @samiura and confirmed this issue has been resolved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/postgresql
Describe the issue you're reporting
Component(s)
receiver/postgresql
Is your feature request related to a problem? Please describe.
PostgreSQL locks often called “write locks” or “exclusive locks,” restrict users from modifying a row or a PostgreSQL table's contents. Rows that have undergone a DELETE or UPDATE operation will be locked solely until the transaction is finished. Hence, this metric will be useful for users to assess the number of locks.
Describe the solution you'd like.
We can query pg_locks, pg_class to count the number of process PIDs
The text was updated successfully, but these errors were encountered: