Postgresql too many locks acquired

Back to Runbooks


This incident type occurs when there are too many locks acquired on a Postgresql database instance. This can cause issues with database performance and functionality. It may be necessary to adjust the max_locks_per_transaction setting in Postgresql to prevent this issue from occurring.



Check the status of the Postgresql service

Check the status of the Postgresql server

Check the number of locks acquired per transaction in the Postgresql database

Check the value of the max_locks_per_transaction setting in the Postgresql configuration file

Check the Postgresql logs for any relevant error messages

A database query is acquiring a large number of locks, causing the lock limit to be exceeded.


Set the new value for max_locks_per_transaction

Update the postgresql.conf file with the new value

Restart the Postgresql service

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.