I just created a new WordPress site in my server. Normally, WordPress uses MyISAM as the database type. But this time, it created all InnoDB tables! Is this normal? Has WordPress switched to InnoDB in the latest versions?


WordPress actually specifies no table type in the create statements, so it uses MySQL's default table engine which is InnoDB from version 5.5 onwards.

  • Shall i keep it that way or change back to MyISAM?
    – THpubs
    Aug 26 '12 at 12:03
  • 1
    That's up to you and depends on your use case - there's a lot of discussion that you can find via Google, but in most cases InnoDB simply is faster.
    – kaiser
    Aug 26 '12 at 12:09
  • 4
    InnoDB is fine, for most cases. Some search plugins will try to add FULLTEXT indexes, and you may need to convert some tables to MyISAM to be able to add those indexes, but if you don't need FULLTEXT then it generally doesn't matter much.
    – Otto
    Aug 26 '12 at 14:23
  • 1
    @Otto: Beating the dead horse: Using since Mysql 5.6 there is FULLTEXT support in InnoDB. (ref: percona.com/blog/2013/02/26/…). Just adding up.
    – hakre
    Feb 13 '17 at 23:25

It matters when it comes to backing up your Wordpress site. I learned this the hard way. If the DB is innodb then R1 cloud restore type backups won't save all the data because it has to be shut down first in order to back it up. Whereas MYISAM can be backed up no problem.

  • @s_ha_dum Never mind, it's useful and should stay here. Only problem: Is there a source or was that learned the hard way? If there's a source, would you mind linking to it?
    – kaiser
    Jun 13 '13 at 17:48
  • This is true for raw backups, but normaly you don't do raw backups of a MySQL database but create a dump instead.
    – Bachsau
    Dec 16 '18 at 7:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.