Berkeley DB 源代码分析 (4) --- 事务和日志

最新推荐文章于 2021-02-16 21:38:10 发布

david_zhao_wei

最新推荐文章于 2021-02-16 21:38:10 发布

阅读量710

点赞数

分类专栏：数据库技术 Berkeley DB 文章标签：代码分析 report each nested

本文链接：https://blog.csdn.net/smartpig_zw/article/details/7392278

版权

本文深入探讨了Berkeley DB的事务处理和日志管理。内容包括：嵌套事务中，子事务无论显式或隐式提交，都会记录__txn_child；只读事务不会写入日志；最外层事务回滚时，所有子事务也会回滚，在恢复过程中可能引发误报；为避免此问题，每个事务需记录__txn_begin来标识父事务ID。此外，还讨论了检查点前后如何记录日志。

摘要由CSDN通过智能技术生成

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