Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Olaf Stein (olaf.steinnationwidechildrens.org)
Date: Mon Feb 16 2009 - 12:12:12 CST
In my experience updating the binaries (or installing the new ones in
addition to the old ones) works fine as long as you have made sure there are
no incompatible changes. I have done this from 5.0 to 5.1 without any
issues. Just run mysql_upgrade and you should be fine.
I have never had to rebuild my indexes so I am not sure about that
On 2/16/09 12:28 PM, "Jim Lyons" <jlyons4435gmail.com> wrote:
> I am beginning the process of upgrading a large mysql 5.0 database to 5.1.
> Specifically, I'm going from 5.0.56 enterprise to 5.1.30 community (which I
> think is now the GA version?)
> The db is about 4 terabytes. This means making a dump of the database,
> installing a new version of the dbms, and reloading the database, would take
> too long. Also the databases are replicating. I believe I need to upgrade
> the slaves first, the go to the master. I've read about the possibility of
> having to rebuild indexes, mainly due to collation changes. I didn't see
> any compatibility issues in going to 5.1.30, although I can certainly
> rebuild some indexes if I need to.
> Can I (after backing up the data) just install the new mysql code, run
> mysql_upgrade, and reasonably expect the database to work?
> What is time involved?
> If I can just install new binaries and point them to the old data, the time
> taken should not depend on the size of the database, should it (unless I
> have to rebuild some indexes)?
----------------------------------------- Confidentiality Notice:
The following mail message, including any attachments, is for the
sole use of the intended recipient(s) and may contain confidential
and privileged information. The recipient is responsible to
maintain the confidentiality of this information and to use the
information only for authorized purposes. If you are not the
intended recipient (or authorized to receive information for the
intended recipient), you are hereby notified that any review, use,
disclosure, distribution, copying, printing, or action taken in
reliance on the contents of this e-mail is strictly prohibited. If
you have received this communication in error, please notify us
immediately by reply e-mail and destroy all copies of the original
message. Thank you.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql