From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OrEHI-0001dN-P0 for garchives@archives.gentoo.org; Thu, 02 Sep 2010 18:12:48 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DEBCFE078E; Thu, 2 Sep 2010 18:12:40 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id A62CCE078E for ; Thu, 2 Sep 2010 18:12:40 +0000 (UTC) Received: by wwf26 with SMTP id 26so942072wwf.10 for ; Thu, 02 Sep 2010 11:12:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=CADdY5HXwBucmKr7qFQjqMoDtwKh05pl5JVPvW89l1g=; b=evDNHUQva/UxcUoP+nb05Wfyb0UlFPTPFC2qQd07REBtLjjeGbDBocO4TwfeUxnUbO vOrwoR/rIPKkvNIcu98inUd8nQKu6FhdErQL7SIgP+yyUxy3fEBRkk8HUPPURmsOKhsR FUV5k3zVPk7eGnz7sjj+D9mA6fJx04sIvxj4I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=fis6u4GUMZFJUAVdHTb2+jPYd9UvsPu8Nr4/Geau1sZ6DaDYfngmIWnvUZLbgEHQax 0BmnTPWGHCw5ywqTIKp5oQ/P+8+xTQMwR6EsGdxsXRycNJtZ7dDu6iZa/eqY+158Cfk5 oTF+JDc7QC02mlBpqK2WXJYYA3jKFVAJZg6E4= Received: by 10.216.22.203 with SMTP id t53mr9621018wet.37.1283451138422; Thu, 02 Sep 2010 11:12:18 -0700 (PDT) Received: from (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id o49sm547487wej.43.2010.09.02.11.12.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Sep 2010 11:12:16 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Proper way of updating mysql from 5.0.90-r2 to 5.1.50? Date: Thu, 2 Sep 2010 19:12:14 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.34-gentoo-r6; KDE/4.4.5; x86_64; ; ) References: <4C7D3C94.2070602@gmail.com> <201009012200.16350.mailingdotlist@gmail.com> <4C7F31AD.9020109@badapple.net> In-Reply-To: <4C7F31AD.9020109@badapple.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2583876.lOO99DLrWu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201009021912.18258.michaelkintzios@gmail.com> X-Archives-Salt: 43df5e9a-3973-4146-914a-fa0b25838668 X-Archives-Hash: f38976c824c288df8f075a5fd550aa97 --nextPart2583876.lOO99DLrWu Content-Type: Text/Plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable On Thursday 02 September 2010 06:10:05 kashani wrote: > On 9/1/2010 1:00 PM, Aniruddha wrote: > > On Tuesday 31 August 2010 20:30:55 Mick wrote: > >>> But this is apparently not the proper way, because after > >>> restarting the server, apache does not show my web-page > >>> reporting there is no such a database. I checked it with > >>> phpmyadmin, and really, there is absolutely no database > >>> in mysql! > >>>=20 > >>> I quickly restored backup version which I have done just > >>> before trying mysql-update, so my web-site is up and running. > >>> Now I would like to update mysql the right way, I but do not > >>> know how to do it... > >>=20 > >> Hi Jarry, > >>=20 > >> Some years ago I ran into some similar problem, I can't recall exactly > >> what. Lost in folklore (wiki?) were some instructions to first stop > >> mysql before you update it and I have been following them since. > >>=20 > >> I stop apach& mysql, run the update, dispatch-conf and then restart > >> them both. Haven't had problems since. > >>=20 > >> There may be a better way for doing this - in which case others who kn= ow > >> better will hopefully chime in. > >=20 > > I'm curious as well. Imo it shouldn't be necessary to stop mysql server > > for each update. >=20 > I did in place upgrades from 5.0.12 or so on up to 5.0.77 or so. You're > unlikely to have problems upgrading Mysql within 5.0.x. If you're moving > up to 5.1, I would definitely stop inserts into Mysql,=20 How do you stop inserts? Would this also apply to MyISAMs or only InnoDB? > dump mysql, stop > mysql, make a copy of /var/lib/mysql just in case, then upgrade to 5.1. > Mysql should be able to upgrade your database in place, but it might > not. If mysql-update doesn't work, importing a dumb is the most reliable > way to get your data into 5.1. > As other people have pointed out you'll need to revdep-rebuild or > preserve the older client libs. >=20 > kashani =2D-=20 Regards, Mick --nextPart2583876.lOO99DLrWu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAkx/6QIACgkQVTDTR3kpaLbJmwCg6vZF+Uup/Cycp9iQNZv8x0Eg G7sAoPDPcamvMy3idDiCCkaOMVC+nXPg =qaN9 -----END PGP SIGNATURE----- --nextPart2583876.lOO99DLrWu--