Skip to content

Commit

Permalink
DOC-1766 read-committed isolation level, v3.6
Browse files Browse the repository at this point in the history
  • Loading branch information
victorleeTG committed May 15, 2023
1 parent 238788e commit c832f3f
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions modules/intro/pages/transaction-and-acid.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,7 @@ The TigerGraph system provides traditional ACID consistency: A transaction can i
The TigerGraph system also provides distributed system Sequential Consistency: every replica of the data performs the same operations in the same order. This is one of the strongest forms of consistency available, stronger than causal consistency, for example.

== *Isolation Level*

TigerGraph supports the Serializable isolation level, the strongest form of isolation. Internally, TigerGraph uses MVCC to implement the isolation. MVCC, or Multi-Version Concurrency Control, makes use of multiple snapshots of portions of the database state in order to support isolated concurrent operations. In principle, there can be one snapshot per read or write operation.
TigerGraph supports the read-committed isolation level, the default standard for many major databases. Internally, TigerGraph uses MVCC to implement the isolation. MVCC, or Multi-Version Concurrency Control, makes use of multiple snapshots of portions of the database state in order to support isolated concurrent operations. In principle, there can be one snapshot per read or write operation.

== *No Dirty Reads*

Expand Down

0 comments on commit c832f3f

Please sign in to comment.