-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
[#9468] [Docs] YSQL: Update docs to include read committed isolation level #10745
Conversation
✔️ Deploy Preview for infallible-bardeen-164bc9 ready! 🔨 Explore the source changes: 47386e8 🔍 Inspect the deploy log: https://app.netlify.com/sites/infallible-bardeen-164bc9/deploys/61a88bf1251ebd00070c5c66 😎 Browse the preview: https://deploy-preview-10745--infallible-bardeen-164bc9.netlify.app/latest/api/ysql/the-sql-language/statements/txn_begin |
@@ -16,31 +16,34 @@ showAsideToc: true | |||
|
|||
Transaction isolation is foundational to handling concurrent transactions in databases. The [SQL-92 standard](https://en.wikipedia.org/wiki/SQL-92) defines four levels of transaction isolation, `SERIALIZABLE`, `REPEATABLE READ`, `READ COMMITTED` and `READ UNCOMMITTED` in decreasing order of strictness. | |||
|
|||
YugabyteDB supports two transaction isolation levels - `SERIALIZABLE` (which maps to the SQL isolation level of the same name) and `SNAPSHOT` (which is mapped to the SQL isolation level `REPEATABLE READ`). Thus, YugabyteDB supports the two strictest of the above four isolation levels. These isolation levels are described below: | |||
YugabyteDB supports three transaction isolation levels - `READ COMMITTED`, `SERIALIZABLE` (both map to the SQL isolation level of the same name) and `SNAPSHOT` (which is mapped to the SQL isolation level `REPEATABLE READ`). Thus, YugabyteDB supports the three strictest of the above four isolation levels. These isolation levels are described below: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pkj415 Not sure where to exactly make the change but we need to call out that READ COMMITTED is in beta and not enabled by default. And possibly call out the flag to enable it too. Otherwise this will confuse users running default YB and getting the wrong semantics (until we actually change the default -- then we'd updates the docs again).
32cd787
to
f21de9f
Compare
f21de9f
to
47386e8
Compare
@m-iancu gentle reminder about this |
@netlify /latest/api/ysql/the-sql-language/statements/txn_begin
@netlify /latest/api/ysql/the-sql-language/statements/txn_set
@netlify /latest/api/ysql/the-sql-language/statements/txn_show
@netlify /latest/architecture/design-goals
@netlify /latest/architecture/transactions/isolation-levels
@netlify /latest/architecture/transactions/transactions-overview
@netlify /latest/benchmark/resilience/jepsen-testing-ysql
@netlify /latest/develop/learn/acid-transactions-ycql
@netlify /latest/develop/learn/acid-transactions-ysql
@netlify /latest/explore/transactions/isolation-levels
@netlify /latest/reference/configuration/yb-tserver