The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-21. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB 10.1.28 Release Notes

The most recent release of MariaDB 10.1 is:
MariaDB 10.1.48 Stable (GA) Download Now

Download Release Notes Changelog Overview of 10.1

Release date: 28 Sep 2017

MariaDB 10.1 is the previous stable 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.28 will be a Stable (GA) release.

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

Thanks, and enjoy MariaDB!

Notable Changes

Updates

  • XtraDB updated to 5.6.37-82.2
  • TokuDB updated to 5.6.37-82.2

Bug Fixes

  • MDEV-13787: Crash in persistent stats wsrep_on (thd=0x0)
  • MDEV-13899: IMPORT TABLESPACE may corrupt ROW_FORMAT=REDUNDANT tables
  • MDEV-13488: InnoDB writes CRYPT_INFO even though encryption is not enabled (fixes upgrades from 5.5 to 10.1)
  • MDEV-13437: InnoDB fails to return error for XA COMMIT or XA ROLLBACK in read-only mode
  • MDEV-13637: InnoDB change buffer housekeeping can cause redo log overrun and possibly deadlocks
  • MDEV-12988: Mariabackup fails if innodb_undo_tablespaces>0
  • MDEV-13471: Test failure on innodb.log_file_size,4k (fixes Galera when using innodb_page_size=4k)
  • MDEV-13814: Extra logging when innodb_log_archive=ON (XtraDB only)
  • MDEV-13807: mariabackup --apply-log-only does generate redo log by performing rollback and possibly other tasks
  • MDEV-13684: InnoDB race condition between fil_crypt_thread and btr_scrub_init

Encryption

  • Temporary files created by merge sort and row log are encrypted if innodb_encrypt_log is set to 1, regardless of whether the table encrypted or not (MDEV-12634).

Notes

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

A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21.

Using page_compression or non-default innodb_page_size created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.

This prevents a downgrade to earlier MariaDB 10.1 versions.

See the commit for details.

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.

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.