Innodb的三把刀之一的DW
The
innodb_doublewrite
variable controls whether the doublewrite buffer is enabled. It is enabled by default in most cases. To disable the doublewrite buffer, set
innodb_doublewrite
to
OFF
. Consider disabling the doublewrite buffer if you are more concerned with performance than data integrity, as may be the case when performing benchmarks, for example.
From MySQL 8.0.30,
innodb_doublewrite
supports
DETECT_AND_RECOVER
and
DETECT_ONLY
settings.
The
DETECT_AND_RECOVER
setting is the same as the
ON
setting. With this setting, the doublewrite buffer is fully enabled, with database page content written to the doublewrite buffer where it is accessed during recovery to fix incomplete page writes.
With the
DETECT_ONLY
setting, only metadata is written to the doublewrite buffer. Database page content is not written to the doublewrite buffer, and recovery does not use the doublewrite buffer to fix incomplete page writes. This lightweight setting is intended for detecting incomplete page writes only.
MySQL 8.0.30 onwards supports dynamic changes to the
innodb_doublewrite
setting that enables the doublewrite buffer, between
ON
,
DETECT_AND_RECOVER
, and
DETECT_ONLY
. MySQL does not support dynamic changes between a setting that enables the doublewrite buffer and
OFF
or vice versa.
If the doublewrite buffer is located on a Fusion-io device that supports atomic writes, the doublewrite buffer is automatically disabled and data file writes are performed using Fusion-io atomic writes instead. However, be aware that the
innodb_doublewrite
setting is global. When the doublewrite buffer is disabled, it is disabled for all data files including those that do not reside on Fusion-io hardware. This feature is only supported on Fusion-io hardware and is only enabled for Fusion-io NVMFS on Linux. To take full advantage of this feature, an
innodb_flush_method
setting of
O_DIRECT
is recommended.
8.0.30之後,支援
DETECT_AND_RECOVER
and
DETECT_ONLY
設定,前者和on設定一樣。
後者表示只記錄後設資料資訊到DW中,只是用來發現不完整的頁。
Fusion-io裝置支援原子寫,DW會自動關閉。只是在Fusion-io硬體上並且只會在Linux的Fusion-io NVMES上開啟
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/30018455/viewspace-2920949/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- show engine innodb status操作解析之一
- mysql innodb lock鎖之record lock之一MySql
- MyISAM被InnoDB替代的重要原因之一是什麼?
- DW_apb_wdt
- 達夢dsc+dw部署
- PostgreSQL的MVCC vs InnoDB的MVCCSQLMVC
- 探索MySQL的InnoDB索引失效MySql索引
- MySQL的show engine innodb statusMySql
- 對Innodb中MVCC的理解MVC
- innodb_support_xa的作用
- MySQL:Innodb:innodb_flush_log_at_trx_commit引數影響的位置MySqlMIT
- MySQL InnoDB的索引擴充套件MySql索引套件
- MySQL InnoDB 中的鎖機制MySql
- MySQL InnoDB搜尋索引的StopwordsMySql索引
- 淺談Innodb的鎖實現
- “20不已 刀行天下”——新華三刀鋒伺服器的“昨天今天明天”伺服器
- 遊戲美術管理的刀與劍遊戲
- 診斷子事務的瑞士軍刀
- 一個價值8.7億刀的bug
- ComponentOne – 控制元件界的“瑞士軍刀”控制元件
- Innodb 下null '' ' '的儲存表現的不同Null
- 墨刀
- 資料分層 ODS DW DM層級
- WordPress問答外掛DW Question Answer分享
- InnoDB 是如何解決幻讀的
- 【Mysql】InnoDB 中的 B+ 樹索引MySql索引
- 【Mysql】InnoDB 引擎中的頁目錄MySql
- undrop-for-innodb恢復drop的表
- Mysql 中 MyISAM 和 InnoDB 的區別MySql
- innodb是如何存資料的?yyds
- InnoDB 中的緩衝池(Buffer Pool)
- MySQL探祕(八):InnoDB的事務MySql
- dw_apb_i2c驅動簡析
- 資料倉儲ODS、DW和DM概念 - 1
- 資料倉儲ODS、DW和DM概念 - 2
- 資料倉儲ODS、DW和DM概念 - 3
- 資料倉儲ODS、DW和DM概念 - 4
- MySQL 配置InnoDB的併發執行緒MySql執行緒