关于LSN的一点研究
2017-10-31 21:50
309 查看
https://dev.mysql.com/doc/refman/5.5/en/glossary.html#glos_lsn
https://www.devarticles.com/c/a/MySQL/How-Logs-Work-On-MySQL-With-InnoDB-Tables/ http://happytest.blog.51cto.com/324097/62848 http://blog.csdn.net/yunhua_lee/article/details/6567869
LSN
Acronym for “log sequence number”. This arbitrary, ever-increasing value represents a point in time corresponding to operations recorded in the redo log. (This point in time is regardless of transaction boundaries; it can fall in the middle of one or more transactions.)
It is used internally by InnoDB during crash recovery and for managing the buffer pool.
Prior to MySQL 5.6.3, the LSN was a 4-byte unsigned integer. The LSN became an 8-byte unsigned integer in MySQL 5.6.3 when the redo log file size limit increased from 4GB to 512GB, as additional bytes were required to store extra size information. Applications
built on MySQL 5.6.3 or later that use LSN values should use 64-bit rather than 32-bit variables to store and compare LSN values.
In the MySQL Enterprise Backup product, you can specify an LSN to represent the point in time from which to take an incremental backup. The relevant LSN is displayed by the output of the mysqlbackup command. Once you have the LSN corresponding to the time of
a full backup, you can specify that value to take a subsequent incremental backup, whose output contains another LSN for the next incremental backup.
See Also buffer pool, crash recovery, incremental backup, MySQL Enterprise Backup, redo log, transaction.
何登成博士画的一张log block的结构图
https://www.devarticles.com/c/a/MySQL/How-Logs-Work-On-MySQL-With-InnoDB-Tables/ http://happytest.blog.51cto.com/324097/62848 http://blog.csdn.net/yunhua_lee/article/details/6567869
LSN
Acronym for “log sequence number”. This arbitrary, ever-increasing value represents a point in time corresponding to operations recorded in the redo log. (This point in time is regardless of transaction boundaries; it can fall in the middle of one or more transactions.)
It is used internally by InnoDB during crash recovery and for managing the buffer pool.
Prior to MySQL 5.6.3, the LSN was a 4-byte unsigned integer. The LSN became an 8-byte unsigned integer in MySQL 5.6.3 when the redo log file size limit increased from 4GB to 512GB, as additional bytes were required to store extra size information. Applications
built on MySQL 5.6.3 or later that use LSN values should use 64-bit rather than 32-bit variables to store and compare LSN values.
In the MySQL Enterprise Backup product, you can specify an LSN to represent the point in time from which to take an incremental backup. The relevant LSN is displayed by the output of the mysqlbackup command. Once you have the LSN corresponding to the time of
a full backup, you can specify that value to take a subsequent incremental backup, whose output contains another LSN for the next incremental backup.
See Also buffer pool, crash recovery, incremental backup, MySQL Enterprise Backup, redo log, transaction.
何登成博士画的一张log block的结构图
相关文章推荐
- 一点关于dll和exe的小研究和小失败
- 关于 Hook Win32 API 的一点研究
- 关于sidebar的一点研究
- 关于JQueryMobile中Slider的一点研究 博客分类:
- 关于C#中readonly的一点小研究
- 关于扩展欧几里得的一点研究
- 关于『65535问题』的一点研究与思考
- 关于移动段设备物理像素和css像素的一点研究
- 关于 Delphi 参数传递方式的一点研究
- 关于 Nim游戏与SG函数 的一点研究
- 关于以太网PAUSE的一点研究
- 关于博客在教学中的应用课题研究的一点小资料(2)。。
- 关于卷积神经网络旋转不变性的一点研究
- 关于博客在教学中的应用课题研究的一点小资料(2)。。
- Android开发,关于启动模式一点研究(Launch Mode)
- 关于博客在教学中的应用课题研究的一点小资料(1)。。
- 关于博客在教学中的应用课题研究的一点小资料(2)。。
- 关于alpha透明的一点研究
- 一点关于最简单的Win32应用程序的研究
- MVC Razor语法的一点研究(关于 @Html.ValidationSummary("",new { @class = "text-danger" }))