MySQL半一致性读原理解析-从源码角度解析

最新推荐文章于 2023-03-14 00:31:36 发布

yzs87

最新推荐文章于 2023-03-14 00:31:36 发布

阅读量1.2k

点赞数 1

分类专栏： MySQL源码分析 MySQL源码研究

本文链接：https://blog.csdn.net/yanzongshuai/article/details/80024543

版权

MySQL源码分析同时被 2 个专栏收录

191 篇文章 87 订阅 ¥9.90 ¥99.00

订阅专栏

MySQL源码研究

123 篇文章 65 订阅 ¥19.90 ¥99.00

订阅专栏

超级会员免费看

本文探讨了MySQL半一致性读的概念，它在更新语句中减少锁冲突和等待，但可能对binlog安全性产生影响。半一致性读发生在RC隔离级别或innodb_locks_unsafe_for_binlog开启时，涉及MySQL和InnoDB层的配合，通过尝试构建和返回记录的prev版本来避免锁等待。同时，文章介绍了其工作原理，包括锁等待条件、索引要求以及在不同情况下的锁处理策略。

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

1、什么是半一致性读

A type of read operation used for UPDATE statements, that is a combination of read committed and consistent read. When an UPDATE statement examines a row that is already locked, InnoDB returns the latest committed version to MySQL so that MySQL can determine whether the row matches the WHERE condition of the UPDATE. If the row matches (must be updated), MySQL reads the row again, and this time InnoDB either locks it or waits for a lock on it. This type of read operation can only happen when the transaction has the read committed isolation level, or when the innodb_locks_unsafe_for_binlog option is enabled.

了解本专栏