Great lecture :) I missed why the combination of No-Steal+No-Force and Steal+Force is not discussed. The paper "Principles of Transaction-Oriented Database Recovery" briefly elaborates on them. Is it the case that modern systems don't fall in those categories anymore?
In steal + force => multiple concurrent transactions will modify but on commit for each tx, we need to flush. Since we are also flushing uncommitted changes of other txs, to keep track of them, we also note them down (like in WAL).. but then it is double write penalty or amplification. :( In no steal + no force => only 1 tx can change a page at a time and on commit we don't flush it => we use WAL for durability => so it is like non concurrent version of steal + no force (WAL) :( seems like both are non-optimal versions.
congratulations and welcome back
thank you Andy
WAL starts from: 41:34
So is the baby yours?
Today I realized that DJ DROP TABLE has to be written on all caps, the way you will write it in SQL while deleting tables. Am I right Andy?
Yes
@@andypavlo I'd always found it a peculiar DJ name. Makes so much more sense now
Congratulations! Like Father Like Son. Long live for you all.
the start is so funny🤣
when the changes we made and recorded inside the wal get reflected to the actual pages of the table ?
Great lecture :)
I missed why the combination of No-Steal+No-Force and Steal+Force is not discussed.
The paper "Principles of Transaction-Oriented Database Recovery" briefly elaborates on them.
Is it the case that modern systems don't fall in those categories anymore?
In steal + force => multiple concurrent transactions will modify but on commit for each tx, we need to flush. Since we are also flushing uncommitted changes of other txs, to keep track of them, we also note them down (like in WAL).. but then it is double write penalty or amplification. :(
In no steal + no force => only 1 tx can change a page at a time and on commit we don't flush it => we use WAL for durability => so it is like non concurrent version of steal + no force (WAL) :(
seems like both are non-optimal versions.
are there any possible no-steal+no-force solutions?
Starts at 3:05