The Ultimate Guide to High Availability with MariaDB

MariaDB 10.1.0 Release Notes

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

Download Release Notes Changelog Overview of 10.1

Release date: 30 Jun 2014

MariaDB 10.1 is the current development series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.

MariaDB 10.1.0 is an Alpha release.

For an overview of MariaDB 10.1 see the What is MariaDB 10.1? page.

Thanks, and enjoy MariaDB!

Notable Changes

This is the first alpha release in the MariaDB 10.1 series.

Notable changes of this release include:

  • InnoDB/XtraDB
    • MDEV-6075, Allow > 16K pages on InnoDB - InnoDB now allows page size to be configured as 16K, 32K and 64K. Note that single row size must be < 16K. This feature will allow especially more blob columns to be created.
    • MDEV-5335, Force PK option - Added a new dynamic configuration variable innodb_force_primary_key default off. If option is true, create table without primary key or unique key where all keyparts are NOT NULL is not accepted. Instead an error message is printed. Variable value can be changed with set global innodb_force_primary_key = <value>.
  • Security
    • MDEV-5730, enhance security using special compilation options - MariaDB is now compiled with security hardening options by default. It is an additional protection layer that makes new, yet unknown, security vulnerabilities more difficult to exploit.
  • Storage Engine functionality
    • MDEV-6107, merge default_tmp_storage_engine - Added default_tmp_storage_engine server variable and the command line option.
    • MDEV-4260, Don't create frm files for temporary tables - Temporary tables no longer create frm files on disk. Which means that if the temporary table is created in MEMORY engine, it will not touch the disk at all.
  • Replication
    • MDEV-5095, Executing triggers on slave in row-based replication - The server has a new command-line option --slave-run-triggers. When slave-run-triggers=yes, execution of row-based events by the slave SQL thread will cause triggers to be invoked. Triggers will be invoked for each row inserted, updated, or deleted. If a trigger fails with an error, replication will stop with an error.
  • Administration
  • Improvements from WebScaleSQL
    • Fix errors detected by ASan at compile time - Not merged but ASan was run against MariaDB. It generated the following:
      • MDEV-6314 - Compile/run MariaDB with ASan (fixed in 10.0.13)
      • MDEV-6315 - TokuDB: ERROR: AddressSanitizer: attempting to call malloc_usable_size() for pointer which is not owned: 0x601200008f80 (not fixed)
      • MDEV-6323 - ‘explain_node’ may be used uninitialized in this function (not fixed)
      • MDEV-6325 - TokuDB: hatoku_hton.cc:1021:5: warning: ‘do_commit’ may be used uninitialized in this function (not fixed)
    • MDEV-6329, Fix errors detected by ASan at runtime. Merged to 5.5.39.
    • Use single quotes for perl paths, in case of special symbols. Merged to 10.0.13.
    • Stop spawning dummy threads on client library initialization. Merged to 10.0.13.
  • Performance

Do not use alpha releases on production systems!

For a complete list of changes made in MariaDB 10.1.0, with links to detailed information on each push, see the changelog.

Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.

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.