最新文章專題視頻專題問答1問答10問答100問答1000問答2000關(guān)鍵字專題1關(guān)鍵字專題50關(guān)鍵字專題500關(guān)鍵字專題1500TAG最新視頻文章推薦1 推薦3 推薦5 推薦7 推薦9 推薦11 推薦13 推薦15 推薦17 推薦19 推薦21 推薦23 推薦25 推薦27 推薦29 推薦31 推薦33 推薦35 推薦37視頻文章20視頻文章30視頻文章40視頻文章50視頻文章60 視頻文章70視頻文章80視頻文章90視頻文章100視頻文章120視頻文章140 視頻2關(guān)鍵字專題關(guān)鍵字專題tag2tag3文章專題文章專題2文章索引1文章索引2文章索引3文章索引4文章索引5123456789101112131415文章專題3
問答文章1 問答文章501 問答文章1001 問答文章1501 問答文章2001 問答文章2501 問答文章3001 問答文章3501 問答文章4001 問答文章4501 問答文章5001 問答文章5501 問答文章6001 問答文章6501 問答文章7001 問答文章7501 問答文章8001 問答文章8501 問答文章9001 問答文章9501
當前位置: 首頁 - 科技 - 知識百科 - 正文

MySQLsoontostoresystemtablesinInnoDB_MySQL

來源:懂視網(wǎng) 責編:小采 時間:2020-11-09 19:19:27
文檔

MySQLsoontostoresystemtablesinInnoDB_MySQL

MySQLsoontostoresystemtablesinInnoDB_MySQL:In the MySQL team, we are changing the system tables currently located in themysqlschema from MyISAM to InnoDB.Looking at this historically:MyISAM was the default storage engine up until MySQL 5.5.In 5.5 almost 4 years ago, the default stor
推薦度:
導(dǎo)讀MySQLsoontostoresystemtablesinInnoDB_MySQL:In the MySQL team, we are changing the system tables currently located in themysqlschema from MyISAM to InnoDB.Looking at this historically:MyISAM was the default storage engine up until MySQL 5.5.In 5.5 almost 4 years ago, the default stor

In the MySQL team, we are changing the system tables currently located in themysqlschema from MyISAM to InnoDB.

Looking at this historically:

  • MyISAM was the default storage engine up until MySQL 5.5.
  • In 5.5 almost 4 years ago, the default storage engine changed to InnoDB, however system tables used for features such as storing privileges and timezones remained as MyISAM.
  • Unlike MyISAM, InnoDB is an ACID compliant storage engine, with the behaviour that once a transaction commits, modifications are able to survive power-loss or other failures. This is a solid foundation to build applications on, since developers will need to handle fewer failures. To use an example:

    1. Customer places an order
    2. A confirmation email is sent
    3. Power is lost

    Without durability, (2) could occur with no record of (1) occurring!Durabilityis a great feature. However, we do not currently offer this for the system tables which use MyISAM. To use an example:

    1. A DBA revokes a user's privilege to MySQL (the command returns success)
    2. Power loss occurs
    3. Upon restore, the revoke never applied.

    By switching to InnoDB we are improving the experience of system-related tasks by ensuring durability that ACID provides.

    This change will have the effect that InnoDB will be required for all MySQL installations, and the configuration setting--skip-innodbwill no longer make sense. Users will still be able to use the MyISAM storage engine, and MyISAM-heavy installations can continue to configure the InnoDB buffer pool toas low as 5MB- taking up very little memory.

    This is a great step forward for MySQL, and I am personally very excited to see this change. Many in the MySQL community have been requesting this change for years, and we're happy to now be working on it. If you have any thoughts, please leave a comment, oremail me!

    聲明:本網(wǎng)頁內(nèi)容旨在傳播知識,若有侵權(quán)等問題請及時與本網(wǎng)聯(lián)系,我們將在第一時間刪除處理。TEL:177 7030 7066 E-MAIL:11247931@qq.com

    本文如未解决您的问题请添加抖音号:51dongshi(抖音搜索懂视),直接咨询即可。

    文檔

    MySQLsoontostoresystemtablesinInnoDB_MySQL

    MySQLsoontostoresystemtablesinInnoDB_MySQL:In the MySQL team, we are changing the system tables currently located in themysqlschema from MyISAM to InnoDB.Looking at this historically:MyISAM was the default storage engine up until MySQL 5.5.In 5.5 almost 4 years ago, the default stor
    推薦度:
    標簽: ta to mysql
    • 熱門焦點
    專題
    Top

    抖音扫码关注

    手机端二维码

    每天分享百科知识!