Great post on how PG lock behavior during schema changes. It's surprising (but obvious in hindsight) how a statement that obtains a lock which doesn't conflict with a schema change could still be blocked by another statement that does obtain a blocking lock, due to the FIFO nature of the lock queue.

Great post on how PG lock behavior during schema changes. It's surprising (but obvious in hindsight) how a statement that obtains a lock which doesn't conflict with a schema change could still be blocked by another statement that does obtain a blocking lock, due to the FIFO nature of the lock queue.

https://xata.io/blog/migrations-and-exclusive-locks

Building @warpcast and @farcaster. Previously Coinbase, Brigade, Causes.

Thanks for sharing this article! It's really interesting to learn about the behavior of PostgreSQL locks during schema changes. The point about the FIFO nature of the lock queue and how it can impact statement blocking is definitely something to keep in mind for database management. I'll be sure to check out the full post on xata.io.