mirror of
https://github.com/janishutz/eth-summaries.git
synced 2026-10-09 05:46:20 +02:00
[DMDB] Notes on concurrency control
This commit is contained in:
1 parent
9ea73f2496
commit
a331b8987f
9 files changed
+27
-7
No files matched your search
@@ -1,5 +1,5 @@
|
||||
\newpage
|
||||
\subsection{Concurrency Control}
|
||||
\subsection{Concurrency Control (CC)}
|
||||
The goal of concurrency control is to ensure the correct executions of concurrent transactions.
|
||||
The baseline for correctness is, as previously mentioned, serial execution.
|
||||
|
||||
@@ -14,7 +14,9 @@ and leaves the DB in a consistent state.
|
||||
\item Conflicting operations of non-aborted transactions are ordered in the same way in both histories
|
||||
\end{enumerate}
|
||||
|
||||
\inlinedefinition[Serializable History] A history is serializable if and only it is equivalent to a serial history.
|
||||
\inlinedefinition[(Conflict) Serializable History] A history is serializable if and only it is equivalent to a serial history.
|
||||
|
||||
A very simple way to check this is that a history is not CS if there are conflicting operations.
|
||||
|
||||
\inlinetheorem[Serializability] A history is serializable if and only if its serializability graph is acyclic.
|
||||
The seerializabililty graph is constructed from the history graph as follows:
|
||||
|
||||
Reference in new issue
Block a user