Add lesson 39: Deadlocks#99
Merged
Merged
Conversation
Part of #6 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Deadlocks (roadmap item
03-deadlocks) — the new Module 9: Concurrency.Summary
Why two transactions can freeze each other, how Postgres detects and breaks the tie, and the ordering discipline that prevents it.
Check
One
query-returnscheck (consistent-order-transfer) — the learner does a consistent-lock-order transfer (the avoidance technique), verified by the resulting balances.Verified end-to-end against a non-superuser Postgres 16.
npm run lessons:validate(34/34) andnext buildboth pass.Part of #6
🤖 Generated with Claude Code