On Thu, Jul 12, 2012 at 10:08 AM, Steve Meyers <[email protected]> wrote: > On 7/12/12 10:00 AM, [email protected] wrote: >> *CTO: Lack of Commitment? (Ubuntu Maverick -- possible Percona Issue)* >> This happened a few months ago-- and our CTO was the person who >> attempted to implement Percona -- I think the problem was that he tried >> to install it without clearing out the databases, then re-importing >> everything (i.e. he just installed percona and kept the existing, old >> mysql tables). This was with Ubuntu Maverick. Anyway, I think it was >> broken in his case because he didn't want to rebuild the database. i.e. >> the issue was likely due to a lack of commitment. > > After upgrading, you should always run mysql_upgrade. It will take care > of any table changes. If you're switching from MySQL to Percona on the > same version #, you usually won't have many (if any) problems.
Very likely missing the upgrade step. Ubuntu Maverick came with MySQL 5.1.63, while the Percona repo for Maverick comes w/ 5.5.17 _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
