1. in nested txns, when child txns of any level commit, __txn_child logs are always written, no matter the child txn commits explicitly or implicitly by its parent's commit.2. Read only txns don
1. in nested txns, when child txns of any level commit, __txn_child logs are always written, no matter the child txn commits explicitly or implicitly by its parent's commit.
2. Read only txns don't write anything into the log because the __txn_regop is only written if any log records are written before the commit.
3. when the outermost txn aborts, all its children aborts. At recovery, we can not figure out the parent-children relationship, and we don't need to know this, we simply regard all abort txns as indepent outermost txns, and undo their changes. However, during verification without this information, we may report false alarms: we may report a parant txn T0's aborted child T1 to be modifying a page owned by T0, since from the log we only know T1 aborted but can't know T1 is child txn of T0.
4. So we have to add a "__txn_begin" log record for each txn to record a txn's parent txnid. But
最低0.47元/天 解锁文章
636
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
