From: Reindl Harald
Date: February 20 2013 5:43pm
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
List-Archive: http://lists.mysql.com/mysql/229018
Message-Id: <51250B3C.5090202@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="----enig2MFFPELCQWPLASSFOXJSE"

------enig2MFFPELCQWPLASSFOXJSE
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 20.02.2013 18:26, schrieb Mike Franon:
> So I did a full mysqldump over the weekend for a second time and this
> time it is 220GB, no clue what happened last time, I should have
> realized looking at the file size something was wrong, but since I got
> no errors did not think about it, and this time I timed it, took 7
> hours to do a complete mysqldump
>=20
> Restoring it is not fun 18+ hours and counting, at this rate it will
> be a week, there has to be a better way of doing this, and this is
> only going form 5.0 to 5.1
>=20
> I know some are saying don't need to do a mysqldump, but if i don't do
> it, the upgrade errors out on 10 tables, and then gives me errors
> about triggers

and did you ALWAYS "mysql_upgarde -root -p" after ANY mysql-update?
at least before try a major upgrade?

did you try "mysqlcheck -h localhost --check-upgrade --all-databases --au=
to-repair --user=3Droot -p"
BEFORE the upgrade? did you try it ALSo after the upgrade?

sorry, i do not believe that dump/import is needed and idoubt
it will not give better results


------enig2MFFPELCQWPLASSFOXJSE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlElCzwACgkQhmBjz394Anlg7wCdHt86GZ+JUzF3BGFrMN5EbenB
hRoAmwXAXcxEPNPlkmIBY5Wy8eJhjkhI
=zeSA
-----END PGP SIGNATURE-----

------enig2MFFPELCQWPLASSFOXJSE--