Finding the root cause of locking problems in Postgres

*Find the article on our blog here:*

https://pganalyze.com/blog/5mins-postgres-find-cause-locking-problems

In E99 of "5mins of Postgres" we're showing how to go about finding the source of a locking problem in Postgres. Specifically, we are looking at how to debug a lock problem, how to end a process that’s holding a lock in Postgres, and show general helpful settings for handling Postgres locking.

*Learn more about pganalyze:*

https://pganalyze.com

https://pganalyze.com/newsletter

https://twitter.com/pganalyze/

*Check out the pganalyze library for eBooks, webinars, and more:*

https://pganalyze.com/resources

📑 *What we have discussed in this episode of 5mins of Postgres:*

*One PID to Lock Them All: Finding the Source of the Lock in Postgres - by Jesse Soyland*

https://www.crunchydata.com/blog/one-pid-to-lock-them-all-finding-the-source-of-the-lock-in-postgres

*Jesse Soyland on Twitter/X*

https://twitter.com/jsoyland

*Postgres Wiki*

https://wiki.postgresql.org/wiki/Main_Page

*Useful queries to analyze PostgreSQL lock trees (a.k.a. lock queues) - by Nikolay Samokhvalov*

https://postgres.ai/blog/20211018-postgresql-lock-trees

*Nikolay Samokhvalov on Twitter/X*

https://twitter.com/samokhvalov

*Lock monitoring in Postgres: Find blocking queries in a lock tree with pganalyze - by Keiko Oda*

https://pganalyze.com/blog/postgres-lock-monitoring

*pganalyze*

https://pganalyze.com/