MariaDB 10.1.46 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: 10 Aug 2020

MariaDB 10.1 is a 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.46 is a Stable (GA) release.

For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.

Thanks, and enjoy MariaDB!

Notable Changes

Variables

• Limit to 255 ().

• Minimum value of raised to 8 (previously 4) so fixed size like and are not truncated for lower values of max_sort_length ().

InnoDB

• updated to 5.6.49

• Fixed corruption in delete buffering ()

• Fixed a deadlock in FLUSH TABLES…FOR EXPORT ()

• InnoDB data file extension is not crash-safe ()

Replication

• Make the binlog dump thread to log into errorlog a requested GTID position ()

• Fix stop of the optimistic parallel slave at requested START-SLAVE-UNTIL position ()

• Properly handle RESET MASTER TO value, when the value exceeds the max allowed 2147483647 ()

Optimizer

• ALTER TABLE ... ANALYZE PARTITION ... with EITS reads and locks all rows ... ()

• Print ranges in the optimizer trace created for non-indexed columns when optimizer_use_condition_selectivity >2 Now the optimizer trace shows the ranges constructed while getting estimates from EITS ()

• LATERAL DERIVED is not clearly visible in EXPLAIN FORMAT=JSON, make LATERAL DERIVED

Other

• is now taken into account for all intermediate calculations. Previously results could be unpredictable. Note that this means results will have a lower precision in some cases - see ()

• updated to 5.6.49-89.0

• updated to 5.6.49-89.0

• MariaDB could crash after changing the query_cache size ()

Changelog

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

Contributors

For a full list of contributors to , see the .

A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.