hybinet wrote:
Azathoth wrote:
I left myisam for transactional Postgres (which, flamebait or not, runs circles around InnoDB) many moons ago after persistent index file corruption required weekly restores from the backup...
I love PostgreSQL too. I wouldn't use any other RDBMS for a new project. But since WordPress can't use PostgreSQL, InnoDB seems to be the next best option even if no transactions are used. At least the tables will be much more corruption-resistant, and reading while writing is also going to be faster.
And as I understand it, InnoDB has row-level locking whereas MyISAM has table-level locking. So, InnoDB should be faster for a situation where you have many read/writes going on. Not sure if that would have much of an impact on Wordpress though, unless it's a Wordpress site that publishes many posts/day.