From owner-freebsd-questions@FreeBSD.ORG Fri Jun 25 05:42:06 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96A1116A4CE for ; Fri, 25 Jun 2004 05:42:06 +0000 (GMT) Received: from galilee.polands.org (CPE-24-208-53-189.new.rr.com [24.208.53.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFA0943D6A for ; Fri, 25 Jun 2004 05:42:05 +0000 (GMT) (envelope-from doug@polands.org) Received: from email.polands.org (samaria.polands.org [172.16.1.17]) by galilee.polands.org (8.12.9/8.12.9) with SMTP id i5P5lNGk073340; Fri, 25 Jun 2004 00:47:23 -0500 (CDT) (envelope-from doug@polands.org) Received: from 172.16.1.35 (SquirrelMail authenticated user djp) by email.polands.org with HTTP; Fri, 25 Jun 2004 00:40:32 -0500 (CDT) Message-ID: <55750.172.16.1.35.1088142032.squirrel@email.polands.org> In-Reply-To: <40DBB6D8.6070004@davidfuchs.ca> References: <40DB608C.3040302@polands.org> <40DBB6D8.6070004@davidfuchs.ca> Date: Fri, 25 Jun 2004 00:40:32 -0500 (CDT) From: "Doug Poland" To: "David Fuchs" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: jester@panix.com cc: freebsd-questions@freebsd.org Subject: Re: Upgrading MySQL strategies X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 05:42:06 -0000 David Fuchs said: > Doug Poland wrote: >> Does someone have a strategy for upgrading MySQL? > > >> I've searched the archives and have turned up nothing useful. One would >> think this would be covered in MySQL's excellent on-line docs, but I >> could find no mention of upgrading. >> > > Hi Doug, > > As a rule, you shouldn't trust that your database will be compatible > with any version of MySQL besides the one it currently runs under. > Dumping the database and re-loading it is the best option. Make sure to > check the changelog for the new version beforehand, just in case there > have been important changes (possible inclusion of new reserved words - > things of that nature). Sometimes there are specific processes you need > to follow for upgrading certain versions of MySQL (i.e. you'll need to > run a contributed script or something) - where applicable, these > processes are well-documented. > > I think a good 'strategy' is the same one you would use for any kind of > upgrade - one that allows you to test your changes safely and thoroughly > before implementing them. Always backup first, of course. Run both the > old and new versions of MySQL side-by-side with separate copies of the > database (you'll need to modify your config appropriately to run two > copies) and take your time with it to ensure things are running as expected. > > Section 2.5 of the MySQL documentation has a lot of good information for > upgrading. You can view the HTML copy (with user comments) here: > > http://dev.mysql.com/doc/mysql/en/Upgrade.html > Thanks for the info. Don't know how I could have missed that URL on MySQL's site. -- Regards, Doug