Oracle 5.0 Reference Manual page 163

• MySQL 5.0.27 is the last version in MySQL 5.0 for which MySQL-Max binary distributions are
provided, except for RPM distributions. For RPMs, MySQL 5.0.37 is the last release. After these
versions, the features previously included in the
If you previously installed a MySQL-Max distribution that includes a server named mysqld-max,
and then upgrade later to a non-Max version of MySQL,
mysqld-max
server manually to ensure that
For upgrades between versions of a MySQL release series that has reached General Availability
status, you can move the MySQL format files and data files between different versions on systems with
the same architecture. For upgrades to a version of a MySQL release series that is in development
status, that is not necessarily true. Use of development releases is at your own risk.
If you are cautious about using new versions, you can always rename your old
installing a newer one. For example, if you are using a version of MySQL 4.1 and want to upgrade
to 5.0, rename your current server from
something unexpected, you can simply shut it down and restart with your old mysqld.
If problems occur, such as that the new
without a password, verify that you do not have an old
You can check this with the
defaults). If this command displays anything other than the program name, you have an active
file that affects server or client operation.
my.cnf
If, after an upgrade, you experience problems with compiled client programs, such as
out of sync
when compiling your programs. In this case, you should check the date for your
libmysqlclient.a
your programs with the new headers and libraries. Recompilation might also be necessary for
programs compiled against the shared client library if the library major version number has changed
(for example from
If your MySQL installation contains a large amount of data that might take a long time to convert after
an in-place upgrade, you might find it useful to create a "dummy" database instance for assessing what
conversions might be needed and the work involved to perform them. Make a copy of your MySQL
instance that contains a full copy of the
your upgrade procedure on this dummy instance to see what actions might be needed so that you can
better evaluate the work involved when performing actual data conversion on your original database
instance.
It is a good idea to rebuild and reinstall the Perl
release of MySQL. The same applies to other MySQL interfaces as well, such as PHP
extensions and the Python
2.19.1.1. Upgrading from MySQL 5.0 to 5.0.10 or Higher
After upgrading a 5.0 installation to 5.0.10 or higher, it is necessary to upgrade your grant tables.
Otherwise, creating stored procedures and functions might not work. The procedure for doing this is
described in
2.19.1.2. Upgrading from MySQL 4.1 to 5.0
server. If you perform such an upgrade, you should remove the old
mysqld_safe
--print-defaults
or unexpected core dumps, you probably have used old header or library files
library to verify that they are from the new MySQL distribution. If not, recompile
libmysqlclient.so.15
MySQLdb
Section 4.4.9, "mysql_upgrade
Note
It is good practice to back up your data before installing any new version of
software. Although MySQL works very hard to ensure a high level of quality, you
should protect your data by making a backup.
To upgrade to 5.0 from any previous version, MySQL recommends that you
dump your tables with
Upgrading MySQL
mysqld-max
mysqld_safe
runs the new
to mysqld-4.1. If your new
mysqld
server does not start or that you cannot connect
mysqld
my.cnf
[240] option (for example,
to libmysqlclient.so.16.
database, plus all other databases without data. Run
mysql
DBD::mysql
module.
— Check Tables for MySQL
before upgrading and reload the dump
mysqldump
143
server are included in mysqld.
still attempts to run the old
mysqld-max
server.
mysqld
mysqld
mysqld
file from your previous installation.
mysqld --print-
mysql.h
module whenever you install a new
Upgrade".
before
then does
Commands
file and
mysql