vBulletin Mods

The Official vBulletin Modifications Site
https://www.vbulletin.org/forum/showthread.php?t=322830

Converting 'post' & 'thread' Tables to InnoDB - MySQL v5.6
by XenonKilla
13 Jun 2016 19:01

I know that the in the past it was impossible to convert the 'post' and 'thread' tables to InnoDB without losing the full-text capabilities. But now I'm reading that the InnoDB engine in MySQL v5.6+ now supports Full-Text. So is it now possible to convert my tables from MyISAM to InnoDB and still retain full-text capabilities? Will everything still function properly or am I missing something here?

Paul M 14 Jun 2016 16:52

Yes its possible, and in fact we did it on vb.org's database a while ago.

XenonKilla 14 Jun 2016 21:02

Hey Paul, Thanks for the response.

Once the 'post' and 'thread' tables are converted to InnoDB is it still possible to convert them back to MyISAM later on down the road if things don't work out?

Also, right now all my tables are using MyISAM (except of course MEMORY tables) so would it be beneficial for me to only convert just my 'post' and 'thread' tables to InnoDB and leave the rest as MyISAM? Or should I just convert everything to InnoDB? I run a pretty large forum and my post table currently has over 1,003,525 rows. The site runs good but I'm know that table locking on the post and thread tables is definitely killing me.

Zachery 15 Jun 2016 00:02

Short answer is yes on converting them back.

You should probably convert your memory tables to INNODB or MyISAM as well. The session table breaks down as a memory table around 50k sessions, not that you're likely to see that on most sites.

XenonKilla 15 Jun 2016 00:20

Good to know, Thanks for the tip!

What about the other tables? I know that both storage engines have their pros and cons but should I just convert them all to InnoDB or would it be more beneficial to just leave them as MyISAM?

AusPhotography 15 Jun 2016 03:01

Yes. 5.6 is good for the change.
A better alternate is MariaDB (if you can) and Aria tables as this is faster.

Paul M 15 Jun 2016 17:03

Quote:

Originally Posted by XenonKilla (Post 2572067)
Good to know, Thanks for the tip!

What about the other tables? I know that both storage engines have their pros and cons but should I just convert them all to InnoDB or would it be more beneficial to just leave them as MyISAM?

Unless they are causing you a problem, leave them alone.

Dont make changes for the sake of making changes.

XenonKilla 15 Jun 2016 17:11

I agree but if something is clearly going to be better then I'd rather do that instead. But yeah MyISAM has been great thus far so I'll probably just leave those other tables alone. Was just fishing for some advice that's all. :)


All times are GMT. The time now is 09:41.

Powered by vBulletin® Version 3.8.14
Copyright © 2020, MH Sub I, LLC dba vBulletin. All Rights Reserved. vBulletin® is a registered trademark of MH Sub I, LLC
Copyright ©2001 - , vbulletin.org. All rights reserved.