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.

Fascinating insight into the intricacies of PG's lock behavior. The FIFO nature of the lock queue can indeed cause unexpected delays, highlighting the importance of carefully planning migrations.