Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updated text to clarify performance vs serializability tradeoff #348

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Updated text to clarify performance vs serializability tradeoff #348

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2a2a6a3
Updated text to clarify performance vs serializability tradeoff
benmeadowcroft Oct 6, 2023
ee352e6
Corrected typo in paragraph
benmeadowcroft Dec 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/deep-dive/distributed-transaction/isolation-level.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ This is the lowest isolation level. In this level, dirty reads are allowed, so o

### Snapshot Isolation

We mentioned 4 different isolation levels above, but TiDB doesn’t adopt any of them. Instead, TiDB uses snapshot isolation as its default ioslation level. The main reason for it is that it allows better serializability, yet still avoids most of the concurrency anomalies that serializability avoids (but not always all).
We mentioned 4 different isolation levels above, but TiDB doesn’t adopt any of them. Instead, TiDB uses snapshot isolation as its default isolation level. The main reason for it is that it allows better performance than serializability, yet still avoids most of the concurrency anomalies that serializability avoids (but not always all).

TiDB is not alone: snapshot isolation also has been adopted by major database management systems such as InterBase, Firebird, Oracle, MySQL, PostgreSQL, SQL Anywhere, MongoDB and Microsoft SQL Server (2005 and later).

Expand Down