Title: MyISAM
Last modified: August 21, 2016

---

# MyISAM

 *  [f.junaid](https://wordpress.org/support/users/fjunaid/)
 * (@fjunaid)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/myisam/)
 * Hi,
 * We are having large database around 800MB, all the tables are innodb but one 
   table “wp_posts” is MyISAM, is it wise to convert it to innodb as well?
 * I mean what will be the consequences?
 * -Regards.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [catacaustic](https://wordpress.org/support/users/catacaustic/)
 * (@catacaustic)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/myisam/#post-4087827)
 * The main differences between the two table types are that MyISAM has faster writing
   speeds because it doesn’t have any built-in foreign key checking, where InnoDB
   has foreign key checking enabled. WordPress doesn’t rely on InnoDB, and is made
   to work correctly with MyISAM by default so there’s not much benifit in using
   InnoDB unless you’re going to be adding in your own tables and you need the foreign
   key checking enabled.
 *  Thread Starter [f.junaid](https://wordpress.org/support/users/fjunaid/)
 * (@fjunaid)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/myisam/#post-4087940)
 * Well I have converted almost all tables to innodb except wp_posts,
 * should I move them to MyISAM once again?

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘MyISAM’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 2 replies
 * 2 participants
 * Last reply from: [f.junaid](https://wordpress.org/support/users/fjunaid/)
 * Last activity: [12 years, 9 months ago](https://wordpress.org/support/topic/myisam/#post-4087940)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics