Skip to content
Why Database Deadlocks Need Wait-Die and Wound-Wait Schemes episode artwork

Jul 23, 2026 11 min

Why Database Deadlocks Need Wait-Die and Wound-Wait Schemes

from Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations Hosted by Fexingo

Lucas and Luna dive into database deadlock handling, comparing wait-die and wound-wait schemes. Using a concrete example from PostgreSQL 17's transaction manager, they explain how these protocols prevent deadlocks without the overhead of a deadlock detector. The episode covers why wait-die is safer for read-heavy workloads while wound-wait favors writes, and how Amazon Aurora's distributed architecture forced a custom hybrid approach. A must-listen for engineers designing high-concurrency OLTP systems. #DatabaseDeadlocks #WaitDie #WoundWait #PostgreSQL #AmazonAurora #OLTP #ConcurrencyControl #LockManager #TransactionIsolation #DeadlockPrevention #DistributedDatabases #DatabaseInternals #TechPodcast #FexingoBusiness #BusinessPodcast #DataEngineering #SQL #NoSQL Keep every episode free: buymeacoffee.com/fexingo

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Why Database Deadlocks Need Wait-Die and Wound-Wait Schemes

0:00 11:13

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations?

This episode is 11 minutes long.

When was this Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations episode published?

This episode was published on July 23, 2026.

Can I download this Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.