PostgreSQL rocks, except when it blocks: Understanding locks
While the open source Postgres database is amazing at running multiple operations at the same time, there are cases in which Postgres needs to block an operation using a lock. This post by Marco Slot & the distributed database team at Citus Data is all about understanding locking behaviors in Postgres.
PostgreSQL rocks, except when it blocks: Understanding locks - Citus Data The schedule is out 🗓️ for POSETTE: An Event for Postgres 2026! Skip navigation SHARE THIS POST Share on X Share on LinkedIn Copy link Get our monthly newsletter On the Citus open source team, we engineers take an active role in helping our users scale out their Postgres database, be it for migrating an existing application or building a new application from scratch . This means we help you with distributing your relational data model—and also with getting the most out of Postgres. One problem I often see
saved by
related reading
- Create an advanced search engine with PostgreSQL | xataxata.io
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- The most useful Postgres extension: pg_stat_statements - Citus Datacitusdata.com
- GitHub - jorzel/concurrency-control: In this repo I would like to show 4 strategies of concurrency control for writing data using Python SQLAlchemy ORM and PostgresSQL (however this examples could be easily transformed to plain SQL).github.com
- How to do distributed locking - Martin Kleppmann's blogmartin.kleppmann.com
- Schedule | POSETTE: An Event for Postgres 2024 - Citus Datacitusdata.com
- The startup's Postgres survival guidehatchet.run
- Nine ways to shoot yourself in the foot with PostgreSQLphilbooth.me
- RLS sounds great until it isn't — PlanetScaleplanetscale.com
- Making 768 servers look like 1 — PlanetScaleplanetscale.com
- Making Postgres 42,000x slower because I am unemployedbyteofdev.com
- Blog — PlanetScaleplanetscale.com