Upgrading MariaDB


As a general rule, to upgrade from one release series to another, go to the next series rather than skipping a series. To upgrade from a release series previous to MariaDB 5.5, upgrade to each successive release series in turn until you have reached MariaDB 5.5, and then proceed with the upgrade to MariaDB 5.6. For example, if you currently are running MariaDB 5.1 and wish to upgrade to a newer series, upgrade to MariaDB 5.5 first before upgrading to 5.6, and so forth. For information on upgrading to MariaDB 5.5, see the MySQL 5.5 Reference Manual.

To upgrade to MariaDB 5.6, use the items in the following checklist as a guide:

You can always move the MariaDB format files and data files between different versions on systems with the same architecture as long as you stay within versions for the same release series of MySQL.

If you are cautious about using new versions, you can always rename your old mysqld before installing a newer one. For example, if you are using a version of MariaDB 5.5 and want to upgrade to 5.6, rename your current server from mysqld to mysqld-5.5. If your new mysqld then does something unexpected, you can simply shut it down and restart with your old mysqld.

If, after an upgrade, you experience problems with compiled client programs, such as Commands out of sync or unexpected core dumps, you probably have used old header or library files when compiling your programs. In this case, check the date for your mysql.h file and libmysqlclient.a library to verify that they are from the new MariaDB distribution. If not, recompile 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 libmysqlclient.so.15 to libmysqlclient.so.16.

If problems occur, such as that the new mysqld server does not start or that you cannot connect without a password, verify that you do not have an old my.cnf file from your previous installation. You can check this with the --print-defaults option (for example, mysqld --print-defaults). If this command displays anything other than the program name, you have an active my.cnf file that affects server or client operation.

If your MariaDB 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 MariaDB instance that contains a full copy of the MariaDB database, plus all other databases without data. Run 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 DBD::mysql module whenever you install a new release of MySQL. The same applies to other MariaDB interfaces as well, such as PHP MariaDB extensions and the Python MySQLdb module.

Retornar