Changes & Improvements in MariaDB 5.5

MariaDB 5.5 is MariaDB 5.3 + MySQL 5.5, with added features. The first stable release was in April 2012, and the final release in May 2020.

For upgrading to MariaDB 10.0, the more recent stable release, see Upgrading from MariaDB 5.5 to MariaDB 10.0.

Feature Comparison Matrix

We have created an Optimizer Feature Comparison Matrix showing the new optimizer features in MariaDB 5.5 and 5.3 compared to MySQL 5.5 and 5.6.

See also a detailed breakdown of System variable differences between MariaDB 5.5 and MySQL 5.5.

New Features

• Significantly more efficient thread pool, comparable in functionality to the closed source feature in MySQL Enterprise.
• Non-blocking client API Library (MWL#192)
• @@skip_replication option (MWL#234)
• SphinxSE updated to version 2.0.4.
• Extended Keys support for XtraDB and InnoDB
• New INSTALL SONAME statement (MWL#77)
• New LIMIT ROWS EXAMINED optimization (MDEV-28)
• mysql_real_connect() Changes
  • In MySQL, and in MariaDB versions before 5.5.21, mysql_real_connect() removes from the MYSQL object any options set with mysql_option() when it fails. Beginning with MariaDB 5.5.21, options are preserved by a failing mysql_real_connect(); use mysql_close(), as normal, to clear them.
  • This only has effect if the MYSQL object is reused after a mysql_real_connect() failure (which is unusual). No real-life incompatibilities are expected from this change (it is unlikely that an application would rely on options being automatically removed between connection attempts).
• The variables replicate_do_*, replicate_ignore_*, and replicate_wild_* have been made dynamic, so they can be changed without requiring a server restart. See Dynamic Replication Variables for more information.
• New status variables for checking if features are used. These are very useful in user feedback to tell developers how much a feature is used:
  • Feature_dynamic_columns
  • Feature_fulltext
  • Feature_gis
  • Feature_locale
  • Feature_subquery
  • Feature_timezone
  • Feature_trigger
  • Feature_xml
• New status variables to see what's going on:
  • Opened_views
  • Executed_triggers
  • Executed_events
• New plugin to log SQL level errors. SQL_ERROR_LOG
• New variable OLD_MODE to set compatibility behavior with older MySQL or MariaDB versions.

Information Schema

There are a number of new INFORMATION SCHEMA tables:

• INNODB_SYS_COLUMNS
• INNODB_SYS_FIELDS
• INNODB_SYS_FOREIGN
• INNODB_SYS_FOREIGN_COLS
• PARAMETERS
• TABLESPACES

Minor Extensions

• Updates to performance schema tables are not stored in the binary log and thus not replicated to slaves. This is to ensure that monitoring of the master will not cause a slower performance on all slaves. This also fixes a crash on the slaves.

New features are added to MariaDB 10.0.

Deprecated / Disabled Features

• PBXT is no longer in the binary builds/distributions. It's however still in the source distributions and in the source tree. The reason is that PBXT is no longer actively maintained, has a few bugs that are not fixed and is not in widespread use.

Switching Between InnoDB and XtraDB

MariaDB 5.5 comes with both XtraDB (compiled in) and InnoDB (as a plugin). By default MariaDB 5.5 uses XtraDB. If you want to switch to use InnoDB you can do:

mysqld --ignore-builtin-innodb --plugin-load=innodb=ha_innodb.so \
--plugin_dir=/usr/local/mysql/lib/mysql/plugin

(plugin_dir should point to where ha_innodb.so is installed)

The above options can of course also be added to your my.cnf file:

[mysqld]
ignore-builtin-innodb
plugin-load=innodb=ha_innodb.so
plugin_dir=/usr/local/mysql/lib/mysql/plugin

If you want you can also compile MariaDB with InnoDB as default.

Security Vulnerabilities Fixed in MariaDB 5.5

The following CVEs are also fixed in MariaDB 5.5 but the fix is not tied to a specific version number:

• CVE-2012-0113
• CVE-2011-2262
• CVE-2012-0116
• CVE-2012-0118
• CVE-2012-0496
• CVE-2012-0115
• CVE-2012-0119
• CVE-2012-0120
• CVE-2012-0484
• CVE-2012-0485
• CVE-2012-0486
• CVE-2012-0487
• CVE-2012-0488
• CVE-2012-0489
• CVE-2012-0490
• CVE-2012-0491
• CVE-2012-0495
• CVE-2012-0112
• CVE-2012-0117
• CVE-2012-0114
• CVE-2012-0492
• CVE-2012-0493
• CVE-2012-0075
• CVE-2012-0494

List of All MariaDB 5.5 Releases

See Also

• Upgrading from MariaDB 5.3 to MariaDB 5.5
• Getting, Installing, and Upgrading MariaDB