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

The most recent release of MariaDB 10.3 is:
MariaDB 10.3.39 Stable (GA) Download Now

Download 10.3.36 Release Notes Changelog Overview of 10.3

Release date: 15 Aug 2022

MariaDB 10.3 is the previous stable series of MariaDB, supported until May 2023, and an evolution of MariaDB 10.2 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL.

MariaDB 10.3.36 is a Stable (GA) release.

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

Thanks, and enjoy MariaDB!

Notable Items

InnoDB

  • InnoDB corruption due to lack of file locking (MDEV-28495)
  • FULLTEXT search with apostrophe, and mandatory words (MDEV-20797)
  • ALTER TABLE IMPORT TABLESPACE corrupts an encrypted table (MDEV-28779)

Replication

  • ER_SLAVE_INCIDENT error is specified now on slave to be seen with SHOW-SLAVE-STATUS (MDEV-21087)
  • INCIDENT_EVENT is no longer binlogged when a being logged transaction can be safely rolledback (MDEV-21443)
  • sequences related row-format events are made to correspond to binlog_row_image (MDEV-28487)

Optimizer

  • 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.

CONNECT

mysql Client

  • New mysql client option, -enable-cleartext-plugin. Option does not do anything, and is for MySQL-compatibility purposes only.

General

Security

When upgrading from MariaDB 10.3.8 or earlier to MariaDB 10.3.9 or higher,
running mysql_upgrade is required due to changes introduced in MDEV-14637.

Changelog

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

Contributors

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

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.