eth-janishutz/eth-summaries
1
0
Fork 0
mirror of https://github.com/janishutz/eth-summaries.git synced 2026-09-10 19:15:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

[DMDB] Link relevant sections in checklist

Browse Source
This commit is contained in:
janishutz
2026-08-15 14:39:02 +02:00
parent 72378555eb
commit 8734e8d264
8 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
semester4/dmdb/parts/05_concurrency-control-recovery/07_recovery-procedures.tex
+1 -1
View File
@@ -8,7 +8,7 @@ It may or may not require both, one or none of UNDO and REDO.
\item \bi{Steal Policy}: An uncommitted transaction is allowed to overwrite the changes of a committed transaction in persistent storage.
This logically means that we need to be able to undo transactions.
\item \bi{Force Policy}: All changes made by a transaction must be in persistent storage before the transaction commits.
This requires flushing all blocks with updates from the transaction and if not in-place, it will require being able to redo the transaction.
This requires flushing all blocks with updates from the transaction and if not in-place (called \bi{No-Force}), it will require being able to redo the transaction.
\item \bi{Steal/No-Force}: UNDO/REDO, is the most common approach
\end{itemize}
If for updates tuples are locked, blocks may still be updatable.