MariaDB 10.0.20 Overview and Highlights

MariaDB 10.0.20 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.20/

This is the eleventh GA release of MariaDB 10.0, and 21st overall release of MariaDB 10.0.

There were no major functionality changes, but there was one security fix, 6 crashing bugs fixed, some general upstream fixes, and quite a few bug fixes, so let me cover the highlights:

  • Security Fix: Client command line option –ssl-verify-server-cert (and MYSQL_OPT_SSL_VERIFY_SERVER_CERT option of the client API) when used together with –ssl will ensure that the established connection is SSL-encrypted and the MariaDB server has a valid certificate. This fixes CVE-2015-3152.
  • Crashing Bug: mysql_upgrade crashes the server with REPAIR VIEW (MDEV-8115).
  • Crashing Bug: Server crashes in intern_plugin_lock on concurrent installing semisync plugin and setting rpl_semi_sync_master_enabled (MDEV-363).
  • Crashing Bug: Server crash on updates with joins still on 10.0.18 (MDEV-8114).
  • Crashing Bug: Too large scale in DECIMAL dynamic column getter crashes mysqld (MDEV-7505).
  • Crashing Bug: Server crashes in get_server_from_table_to_cache on empty name (MDEV-8224).
  • Crashing Bug: FreeBSD-specific bug that caused a segfault on FreeBSD 10.1 x86 (MDEV-7398).
  • XtraDB upgraded to 5.6.24-72.2
  • InnoDB updated to InnoDB-5.6.25
  • Performance Schema updated to 5.6.25
  • TokuDB upgraded to 7.5.7

Given the security fix, you may want to consider upgrading if that particular CVE is of concern to you. Also, please review the crashing bugs to see if they might affect you, and upgrade if so. Also, if running TokuDB, XtraDB, InnoDB, or Performance Schema, you may also want to benefit from those fixes, as well as the new MariaDB fixes (139 in all).

You can read more about the 10.0.20 release here:

https://mariadb.com/kb/en/mariadb-10020-release-notes/

And if interested, you can review the full list of changes in 10.0.20 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10020-changelog/

Hope this helps.

MariaDB 10.0.19 Overview and Highlights

MariaDB 10.0.19 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.19/

This is the tenth GA release of MariaDB 10.0, and 20th overall release of MariaDB 10.0.

This was a quick release in order to get a fix for a mysql_upgrade bug (MDEV-8115) introduced in 10.0.18, so there is that, and only 9 other bug fixes.

Here are the main items of note:

  • Fixed the server crash caused by mysql_upgrade (MDEV-8115)
  • Connect upgraded to 1.03.0007

Due to the mysql_upgrade bug fix as well as all of the fixes in MariaDB 10.0.18 (including 5 Security fixes), I would definitely recommend upgrading to this if you are running a prior version of MariaDB 10.0, especially 10.0.18.

You can read more about the 10.0.19 release here:

https://mariadb.com/kb/en/mariadb-10019-release-notes/

And if interested, you can review the full list of changes in 10.0.19 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10019-changelog/

Hope this helps.

 

MariaDB 10.0.18 Overview and Highlights

MariaDB 10.0.18 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.18/

This is the ninth GA release of MariaDB 10.0, and 19th overall release of MariaDB 10.0.

There were no major functionality changes, but there were some general improvements, several security fixes, plus a 10.0.18 mysql_upgrade caution, and quite a few bug fixes, so let me cover what I feel are the main items of note:

  • Security Fixes: Fixes for the following security vulnerabilities:
  • InnoDB upgraded to 5.6.24
  • XtraDB upgraded to 5.6.23-72.1
  • Spider upgraded to 3.2.21
  • mroonga upgraded to 5.02
  • Performance Schema upgraded to 5.6.24
  • Connect upgraded to 1.03.0006
  • Deprecation Notice: As per the MariaDB Deprecation Policy, this will be the final release of MariaDB 5.5 for Fedora 19 “Schrödinger’s Cat”, Ubuntu 10.04 LTS “Lucid”, and Mint 9 LTS “Isadora”. When the next version of MariaDB 5.5 is released, repositories for these distributions will go away.
  • Important mysql_upgrade Caution: The mysql_upgrade in this version introduced a serious bug which affects mysql_upgrade. If already running a MariaDB 5.5.x version, then you can safely skip running mysql_upgrade. However, if migrating from MySQL to MariaDB 5.5, then note this bug. For this specific bug, the problem appears if the targeted databases include data structures such as views with binary or text blobs. The malfunction is in the REPAIR VIEW statement which the script calls.
    • The fix will appear in MariaDB 5.5.44, which will be available soon (MariaDB 5.5.44 includes all MySQL 5.5.44 fixes, so it will be available very shortly after MySQL 5.5.44 is released).

Given the security fixes, if you are running a prior version of 10.0, I would recommend upgrading. However, due to the mysql_upgrade bug in this version, I recommend upgrading to
10.0.19 instead (as it contains the fix for this bug).

You can read more about the 10.0.18 release here:

https://mariadb.com/kb/en/mariadb-10018-release-notes/

And if interested, you can review the full list of changes in 10.0.18 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10018-changelog/

Hope this helps.

 

MariaDB 10.0.17 Overview and Highlights

MariaDB 10.0.17 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.17/

This is the eighth GA release of MariaDB 10.0, and 18th overall release of MariaDB 10.0.

For the most part, there are not a whole lot of new changes to report for this release, but there is a new version of the Audit Plugin and many other engines have been updated as well.

Here are the main items of note:

  1. The new version of the Audit Plugin is 1.2 is included with the following new features:
    • In the audit log passwords are now masked, i.e. the password characters are replaced with asterisks.
    • It’s now possible to filter logging to include only DDL (CREATE, ALTER, etc.) or DML (INSERT, UPDATE, etc.) statements.
    • For more information please refer to the About the MariaDB Audit Plugin page. The plugin is disabled by default.
  2. InnoDB upgraded to 5.6.23
  3. XtraDB upgraded to 5.6.22-72.0
  4. TokuDB upgraded to 7.5.5
  5. mroonga upgraded to 5.0
  6. Spider upgraded to 3.2.18
  7. Connect upgraded to 1.03.0005
  8. HeidiSQL upgraded to 9.1
  9. –galera-sst-mode option removed from mysqldump (MDEV-7615)
  10. mysqlbinlog –binlog-row-event-max-size support added (MDEV-6703)

Overall, there are no critical nor security related bugs fixes, so that is great. As for upgrading, if you’re using any of the above storage engines or the audit plugin, it would be a good idea to consider upgrading (at least review the fixes applicable to you to determine if they will be worth it or not).

You can read more about the 10.0.17 release here:

https://mariadb.com/kb/en/mariadb-10017-release-notes/

And if interested, you can review the full list of changes in 10.0.17 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10017-changelog/

Hope this helps.

 

MariaDB 10.0.16 Overview and Highlights

MariaDB 10.0.16 was recently released (~1.5 months ago on 1/27/2015 – sorry for the delay on my end – I was just extra busy in my spare time recently), and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.16/

This is the seventh GA release of MariaDB 10.0, and 17th overall release of MariaDB 10.0.

For the most part, there are not a whole lot of changes to report for this release, but there are 2 enhancements of note – one being the JSON table type (still *experimental*) and the other a new variable to aid with index statistics calculations on large tables, as well as some security fixes.

Here are the main items of note:

  1. Updates to the CONNECT handler (supporting the JSON table type) – which is *experimental* currently
  2. The innodb_stats_traditional system variable enables a larger sample of pages for larger tables for the purposes of index statistics calculation.
  3. InnoDB upgraded to 5.6.22
  4. XtraDB upgraded to 5.6.22-71.0
  5. TokuDB upgraded to 7.5.4
  6. Fixes for the following security vulnerabilities:

Given the security fixes, you should plan on upgrading if you’re running a prior version of 10.0.

You can read more about the 10.0.16 release here:

https://mariadb.com/kb/en/mariadb-10016-release-notes/

And if interested, you can review the full list of changes in 10.0.16 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10016-changelog/

Hope this helps.

 

MariaDB 10.0.15 Overview and Highlights

MariaDB 10.0.15 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.15/

This is the sixth GA release of MariaDB 10.0, and 16th overall release of MariaDB 10.0.

This release has an important InnoDB/XtraDB fix, a new addition, security enhancements (and improvement) – all related to yaSSL, so be sure to check out these fixes if you’re running MariaDB 10.0, and not up to 10.0.15 yet. (MariaDB 10.0 is the current stable series of MariaDB. It is an evolution of the MariaDB 5.5 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6.)

Here are the main items of note:

  1. This release fixes a serious bug in InnoDB and XtraDB that sometimes could cause a hard lock up of the server (MDEV-7026)
  2. This is the first release that includes Mroonga full-text search storage engine.
  3. When compiled with OpenSSL, MariaDB now supports TLSv1.2 protocol. Limit it to TLSv1.2 ciphers only with –ssl_cipher=TLSv1.2. Limit it to SSLv3 ciphers with –ssl-cipher=SSLv3. RPM and DEB packages from MariaDB.org are built with OpenSSL, others (for Windows and generic Linux) are built with yaSSL.
  4. Fixes for the following security vulnerabilities:
  5. Bundled PCRE is upgraded to 8.36
  6. InnoDB upgraded to 5.6.21
  7. XtraDB upgraded to 5.6.21-70.0
  8. TokuDB upgraded to 7.5.3
  9. SphinxSE upgraded to 2.2.6
  10. Updates to the CONNECT handler including:
  11. We now offer openSUSE repos, see the repository configuration tool for details on how to use it.

Given the severe InnoDB/XtraDB bug, if you’re running a prior MariaDB 10.0 version, I’d recommend upgrading (assuming you’re using InnoDB). Likewise, if you’re using SSL. And then there were a number of fixes to other fixes for TokuDB, CONNECT, and Sphinx, so if you’re using those technologies, you may want to consider upgrading as well.

You can read more about the 10.0.15 release here:

https://mariadb.com/kb/en/mariadb-10015-release-notes/

And if interested, you can review the full list of changes in 10.0.15 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10015-changelog/

Hope this helps.