My website is popular, but a few hours downtime isn’t the end of the world. I don’t have any other boxes that I can test on, and don’t really want to go to the trouble of creating a VM. I’m happy just to backup and do it live on the production box, knowing I can undo it all and revert back to MySQL 5.0 if need be.
I feel all of my database usage is pretty standard - I doubt there will be any compatibility issues with my SQL as it’s just run-of-the-mill select/update/deletes etc. I’ll obviously test it thoroughly once I’m up and running though.
So, any pointers? I feel I should just do a sql dump, uninstall mysql, install percona, and load the db back in from that batch file? Is this a terrible idea? Educate me!
I’m glad this worked well for you. mysql/mysqld is because we distribute RPM and Debian packages which are built the same as MySQL Enterprise, so Percona Server is a seamless replacement for MySQL Enterprise. Debian, Red Hat, and all the others distribute their own customizations, some of which are not even documented well, some of which are pretty brain dead. We want to stay close to Oracle’s version. DBAs who are using Oracle’s binaries don’t want to switch away from what they are used to, and we don’t want to support a variety of different packages.