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.8.1 Release Notes

Download Release Notes Changelog Overview of 10.8

Release date: 9 Feb 2022

This release is no longer available for download after a problem was noticed when manually running mariadb-upgrade. See MDEV-27789 for more details.

Please use a later release.

Do not use non-stable (non-GA) releases in production!

MariaDB 10.8 is the current development series of MariaDB. It is an evolution of MariaDB 10.7 with several entirely new features.

MariaDB 10.8.1 is a Release Candidate (RC) release.

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

Thanks, and enjoy MariaDB!

Notable Items

InnoDB

Optimizer

  • Support descending indexes in the range optimizer (MDEV-26996)

Galera

  • Galera updated to 26.4.11
  • Galera SST scripts should use ssl_capath (not ssl_ca) for CA directory (MDEV-27181)
  • Alter Sequence do not replicate to another nodes with in Galera Cluster (MDEV-19353)
  • Galera crash - Assertion. Possible parallel writeset problem (MDEV-26803)
  • CREATE TABLE with FOREIGN KEY constraint fails to apply in parallel (MDEV-27276)
  • Galera cluster node consider old server_id value even after modification of server_id [wsrep_gtid_mode=ON] (MDEV-26223)

Replication

  • Seconds behind master corrected from artificial spikes at relay-log rotation (MDEV-16091)
  • Statement rollback in binlog when transaction creates or drop temporary table is set right (MDEV-26833)
  • CREATE-or-REPLACE SEQUENCE is made to binlog with the DDL flag to stabilize its parallel execution on slave (MDEV-27365)
  • ALTER is optionally made to binlog in two parts to decrease its replication latency (MDEV-11675)
  • mysqlbinlog --start-position and --stop-position accept gtid values to allow specifying the replication event range in terms of gtid (MDEV-4989)

Packaging & Misc

Docker Library

  • Faster initialization by disabling binary logging during initialization (MDEV-27074)
  • mysql_upgrade can be run if needed using the environment variable MARIADB_AUTO_UPGRADE=1 (MDEV-25670)
  • A healthcheck script /usr/local/bin/healthcheck.sh is installed in the container with various checking options (MDEV-25434)
  • mysql@localhost user is created with the environment variable MARIADB_MYSQL_LOCALHOST_USER=1 and additional grants (beyond USAGE) with MARIADB_MYSQL_LOCALHOST_GRANTS={global grant list} (MDEV-27732)
  • skip innodb buffer pool loads/dumps on temporary startup/shutdown for faster startup/initialization, and accurate "healthcheck.sh --innodb_buffer_pool_loaded"
  • change group ownership on datadir/socket dir (issue #401)
  • log note about note on Securing system users, mysql_secure_installation not required (reddit suggestion)
  • speed up Docker Library initialization of timezones (MDEV-27608, MDEV-23326)
  • MariaDB names of executable programs and scripts used instead of historical mysql ones

Changelog

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

Contributors

For a full list of contributors to MariaDB 10.8.1, see the MariaDB Foundation release announcement.

Do not use non-stable (non-GA) releases in production!

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.