MariaDB 11.1.1 Release Notes

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

Download Release Notes Changelog Overview of 11.1

Release date: 6 Jun 2023

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

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

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

Thanks, and enjoy MariaDB!

Notable Items

InnoDB

  • Server crashes in st_join_table::choose_best_splitting (MDEV-31403)
  • Crash with condition pushable into derived and containing outer reference (MDEV-31240)
  • Crash with EXPLAIN EXTENDED for multi-table update of system table (MDEV-31224)
  • InnoDB does not free UNDO after the fix of MDEV-30671 (MDEV-31234)
  • InnoDB hang fixes (MDEV-31158, MDEV-31343, MDEV-31350)
  • Innodb_buffer_pool_read_requests is not updated correctly (MDEV-31309)
  • InnoDB monitor trx_rseg_history_len was accidentally disabled by default (MDEV-31308)
  • Revert "MDEV-30473 : Do not allow GET_LOCK() / RELEASE_LOCK() in cluster"

Changelog

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

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.

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.