Re: MySQL 4.1 to 5.1 large scale upgrade
Posted by: Jcink Cink
Date: April 02, 2011 02:34PM

I probably will not end up converting to InnoDB into all one file, but thanks for the information on it.

In some ways that could actually make things worse for me in the future. As it stands, since they're all seperate files repairs can even be issued individually, and even on the fly. Some repairs are much faster than others, so say a forum 5gb in size doesn't have to suffer with as much downtime as one that's maybe only 300MB. Bummer about the disk space aspect too. Also, this makes me sad:


Backup scripts may need checking. A MyISAM table can be backed up by copying three files. There is no corresponding technique with InnoDB. Similarly, capturing a table or database for copying from production to a development environment is not possible. Change to mysqldump.

I've been doing that right now to even test what we've been going over.

We'll just see how this upgrade goes...

I have considered splitting it into a thousand databases or more before but I have absolutely no idea what that might do in regard to performance. Also the way I look at it, even if I split it up into all the databases, I pretty much have the same exact problem anyway. It's going to take time to SHOW TABLES on all of them and then run upgrades. In theory I guess each one could have rolling upgrades to a degree but I don't think it's worth it.

Options: ReplyQuote

Written By
Re: MySQL 4.1 to 5.1 large scale upgrade
April 02, 2011 02:34PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.