What is MariaDB 5.5?

You are viewing an old version of this article. View the current version here.

Monty Program has a What is MariaDB 5.5? whitepaper available for download.

DateReleaseStatusRelease NotesChangelog
12 Mar 2013MariaDB 5.5.30Stable (GA)Release NotesChangelog
30 Jan 2013MariaDB 5.5.29Stable (GA)Release NotesChangelog
29 Nov 2012MariaDB 5.5.28aStable (GA)Release NotesChangelog
22 Oct 2012MariaDB 5.5.28Stable (GA)Release NotesChangelog
7 Sep 2012MariaDB 5.5.27Stable (GA)Release NotesChangelog
22 Jun 2012MariaDB 5.5.25Stable (GA)Release NotesChangelog
31 May 2012MariaDB 5.5.24Stable (GA)Release NotesChangelog
11 Apr 2012MariaDB 5.5.23Stable (GA)Release NotesChangelog
29 Mar 2012MariaDB 5.5.22Release CandidateRelease NotesChangelog
16 Mar 2012MariaDB 5.5.21BetaRelease NotesChangelog
25 Feb 2012MariaDB 5.5.20AlphaRelease NotesChangelog

MariaDB 5.5 is MariaDB 5.3 + MySQL 5.5, with added features.

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.

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
  • New LIMIT ROWS EXAMINED optimization.
  • 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

Minor extensions

  • Updates to performance schema tables are not stored in 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 not anymore in the binary builds/distributions. It's however still in the source distributions and in the source tree. The reason is that PBXT is not actively maintained anymore, it has a few bugs that are not fixed and it's not that much in use.

You can easily switch 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.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.