From 2a2a6a3293407c280da87a2837a0fc8186957d45 Mon Sep 17 00:00:00 2001 From: Ben Meadowcroft Date: Fri, 6 Oct 2023 11:26:15 -0700 Subject: [PATCH 1/2] Updated text to clarify performance vs serializability tradeoff Signed-off-by: Ben Meadowcroft --- content/deep-dive/distributed-transaction/isolation-level.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/deep-dive/distributed-transaction/isolation-level.md b/content/deep-dive/distributed-transaction/isolation-level.md index 35f0ee6a..e53f7f47 100644 --- a/content/deep-dive/distributed-transaction/isolation-level.md +++ b/content/deep-dive/distributed-transaction/isolation-level.md @@ -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 ioslation 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). From ee352e67ee8b619c336d9494c227ab97e8562984 Mon Sep 17 00:00:00 2001 From: Ben Meadowcroft Date: Fri, 22 Dec 2023 10:36:31 -0800 Subject: [PATCH 2/2] Corrected typo in paragraph Signed-off-by: Ben Meadowcroft --- content/deep-dive/distributed-transaction/isolation-level.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/deep-dive/distributed-transaction/isolation-level.md b/content/deep-dive/distributed-transaction/isolation-level.md index e53f7f47..9df4c79a 100644 --- a/content/deep-dive/distributed-transaction/isolation-level.md +++ b/content/deep-dive/distributed-transaction/isolation-level.md @@ -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 performance than 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).