MariaDB 10.10.1 Release Notes

Download 10.10.1 Release Notes Changelog Overview of 10.10

Release date: 22 Aug 2022

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

MariaDB 10.10 is a current short-term support development series of MariaDB. It is an evolution of MariaDB 10.9 with several entirely new features.

MariaDB 10.10.1 is a Release Candidate (RC) release.

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

Thanks, and enjoy MariaDB!

Notable Items




  • Possible to write/update with read_only=ON and not a SUPER privilege (MDEV-28546)
  • Node crashes with Transport endpoint is not connected mysqld got signal 6 (MDEV-25068)
  • Galera4 not able to report proper wsrep_incoming_addresses (MDEV-20627)
  • Galera should replicate nextval()-related changes in sequences with INCREMENT <> 0, at least NOCACHE ones with engine=InnoDB (MDEV-27862)
  • Add support for OpenSSL 3.0 in Galera (MDEV-25949)
  • Implement a method to add IPs to allowlist for Galera Cluster node addresses that can make SST/IST requests (MDEV-27246)


  • Server crash in JOIN_CACHE::free or in copy_fields (MDEV-23809)
    • Queries that use DISTINCT and an always-constant function like COLLATION(aggegate_func(...)) could cause a server crash. Note that COLLATION() is a special function - its value is constant even if its argument is not costant.
  • Crash when using ANY predicand with redundant subquery in GROUP BY clause (MDEV-29139)
    • A query with a subuquery in this form could cause a crash:
... ANY (SELECT ... GROUP BY (SELECT redundant_subselect_here)) ...
  • MariaDB Server SEGV on INSERT .. SELECT (MDEV-26427)
    • Certain queries in form "INSERT ... SELECT with_aggregate_or_window_func" could cause a crash.
  • restore_prev_nj_state() doesn't update cur_sj_inner_tables correctly (MDEV-28749)
    • Subquery semi-join optimization could miss LooseScan or FirstMatch strategies for certain queries.
  • Optimizer uses all partitions after upgrade to 10.3 (MDEV-28246)
    • For multi-table UPDATE or DELETE queries, the optimizer failed to apply Partition Pruning optimization for the table that is updated or deleted from.
  • Range optimizer regression for key IN (const, ....) (MDEV-25020)
    • The issue can be observed on MariaDB 10.5.9 and later versions which have the fix for MDEV-9750. That fix introduceds optimizer_max_sel_arg_weight.
    • If one sets optimizer_max_sel_arg_weight to a very high value or zero (which means "unlimited") and runs queries that produce heavy-weight graphs, they can observe a performance slowdown, e.g.:
table.keyXpartY [NOT] IN ( ... )
  • Wrong result with table elimination combined with not_null_range_scan (MDEV-28858)
    • If one runs with optimizer_switch='not_null_range_scan=on' (which is not enabled by default), a query that does a join and has const tables could produce a wrong result.
  • Assertion `tmp >= 0' failed in best_access_path (MDEV-28882)
    • If one uses histogram_type=JSON_HB, has collected a histogram of that type and runs a query that selects a very narrow range near histogram end, they can hit an assertion in the optimizer due to rounding errors in the histogram causing negative selectivity.



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


For a full list of contributors to MariaDB 10.10.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' 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 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.