MariaDB 10.3 is no longer maintained. Please use a more recent release.

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

MariaDB 10.3 is a previous major stable version. The first stable release was in May 2018, and it was maintained until May 2023.

For details on upgrading from MariaDB 10.2, see Upgrading from MariaDB 10.2 to 10.3.

MariaDB Server 10.3 is included in MariaDB TX 3.0. Watch the webinar recording to learn more about the new features included in this release.

The following lists the major new features in MariaDB 10.3:

Implemented Features

Sequences

• Sequences Overview (MDEV-10139)

• CREATE SEQUENCE

• SHOW CREATE SEQUENCE

• ALTER SEQUENCE

• DROP SEQUENCE

• NEXT VALUE FOR

• PREVIOUS VALUE FOR

• SETVAL()

Syntax / General Features

• System-versioned tables (also known as AS OF) (MDEV-12894)

• Table Value Constructors (MDEV-12172) — GSoC 2017 project by Galina Shalygina

• Transform [NOT] IN predicate with long list of values INTO [NOT] IN subquery (MDEV-12176) — GSoC 2017 project by Galina Shalygina

• ROW TYPE OF now supports local SP variables (MDEV-14139)

• Aggregate stored functions (MDEV-7773) — GSoC 2016 project by Varun Gupta

• Support for LIMIT clause in GROUP_CONCAT() (MDEV-11297)

• PERCENTILE_CONT, PERCENTILE_DISC, and MEDIAN window functions (MDEV-12985)

• FOR ... END FOR statement (MDEV-14415)

• XA RECOVER FORMAT='SQL' (MDEV-14593)

• Oracle compatible SUBSTR() function (MDEV-14012) — contribution by Jérôme Brauge

• INVISIBLE columns (MDEV-10177) — GSoC 2016 project by Sachin Setiya

• Various scalability improvements (MDEV-14529, MDEV-14505)

• Semi-sync plugin merged into the server (MDEV-13073) — contribution by Alibaba

• INTERSECT and EXCEPT. These are both now reserved words and can no longer be used as an identifier without being quoted (MDEV-10141)

• ROW data type for stored routine variables (MDEV-10914, MDEV-12007, MDEV-12291)

• TYPE OF and ROW TYPE OF anchored data types for stored routine variables (MDEV-12461)

• Cursors with parameters (MDEV-12457)

• DDL Fast Fail - WAIT/NOWAIT (MDEV-11379, MDEV-11388)

• CHR() function (MDEV-12685)

• DELETE statement can delete from the table that is used in a subquery in the WHERE clause (MDEV-12137)

• Stored routine parameters can use ROW TYPE OF (MDEV-13581)

• The server now supports the PROXY protocol - see also the new proxy_protocol_networks system variable (MDEV-11159)

• Instant ADD COLUMN (MDEV-11369) — Tencent Game DBA Team, developed by vinchen.

• UPDATE statements with the same source and target (MDEV-12874) — from Jerome Brauge.

• ORDER BY and LIMIT in multi-table update (MDEV-13911)

• DATE_FORMAT(date, format, locale) - 3 argument form of DATE_FORMAT (MDEV-11553)

• The MariaDB SQL/PL stored procedure dialect (enabled with sql_mode=ORACLE) now supports Oracle style packages. Support for the following statements has been added (MDEV-10591):

  • CREATE PACKAGE

  • CREATE PACKAGE BODY

  • DROP PACKAGE

  • DROP PACKAGE BODY

  • SHOW CREATE PACKAGE

  • SHOW CREATE PACKAGE BODY

• New sql_mode SIMULTANEOUS_ASSIGNMENT to make the SET part of the UPDATE statement evaluate all assignments simultaneously, not left-to-right.

• Correctness improvement - TRUNCATE honors transactional locks (MDEV-15061)

• Windows binaries now use high-precision timer when available (MDEV-15694). This makes much less probable for two queries to have the same CURRENT_TIMESTAMP(6) value, for example.

• Two new ALTER TABLE ... ALGORITHM options, INSTANT and NOCOPY, which allow operations that would require any data files to be modified, or that would require rebuilding the clustered index respectively, to be refused rather than potentially perform slowly (MDEV-13134)

• mysqldump --ignore-database option (MDEV-13336)

Compatibility

• As a result of implementing Table Value Constructors, the VALUES function has been renamed to VALUE() (MDEV-12172)

• When running with sql_mode=ORACLE, the server now understands a subset of Oracle's PL/SQL language instead of the traditional MariaDB syntax for stored routines. See MDEV-10142, MDEV-10764 and SQL_MODE=ORACLE From MariaDB 10.3 to know the current status.

• New sql_mode, EMPTY_STRING_IS_NULL.

• INTERSECT and EXCEPT are both now reserved words and can no longer be used as an identifier without being quoted (MDEV-10141)

• Functions that used to only return 64-bit now can return 32-bit results (MDEV-12619).

Compression

• Storage-engine Independent Column Compression (MDEV-11371) — Tencent Game DBA Team, developed by willhan, also thanks to AliSQL.

• On Linux, shrink the core dumps by omitting the InnoDB buffer pool (MDEV-10814)

Encryption

• Temporary files created by merge sort and row log are encrypted if innodb_encrypt_log is set to 1, regardless of whether the table encrypted or not (MDEV-12634).

Optimizer/Performance

• Condition pushdown through PARTITION BY clause of window functions (MDEV-10855)

• New Lateral Derived optimization was introduced.

• Numerous performance improvements for high-concurrency load

• Numerous scalability and performance improvements to global data structures, including MDEV-14756, MDEV-15019, MDEV-14482, MDEV-15059, MDEV-15104

• Performance improvements to persistent data structures: MDEV-15090, MDEV-15132

Storage Engines

InnoDB

• innodb_fast_shutdown now has a new mode, 3, which skips the rollback of connected transactions (MDEV-15832)

Spider

The Spider storage engine has been updated to 3.3.13. The partitioning storage engine has been updated to support all the new Spider features including:

• Direct join support. This allows Spider to do JOINS and GROUP BYs internally.

• Direct update and delete.

• Direct aggregates.

• slave_transaction_retry_errors and slave-transaction-retry-interval allow more control over handling delays or conflicts when applying binary logs.

Most of the features were done as part of MDEV-7698.

OQGRAPH

• OQGraph now supports the "leaves" algorithm (MDEV-11271) — contribution by Heinz Wiesinger

Partition Engine

• Numerous improvements for the partition engine (MDEV-7698) — contribution by Kentoku Shiba

  • Full text support.

  • Multi-range-read (Gives better performance when handling multiple ranges).

  • Support for condition pushdown.

  • HANDLER support

• Aggregate pushdown

• Bulk update/delete

Information Schema

• The Information Schema is optimized to use much less memory when selecting from INFORMATION_SCHEMA.TABLES or any other table with many VARCHAR or TEXT columns (MDEV-14275)

• The Information Schema Columns table now displays system versioning info in the EXTRA column - MDEV-15062

Logging

• Disable logging of certain statements to the general log or the slow query log with the log_disabled_statements and log_slow_disabled_statements system variables.

• A new option to log_slow_filter, filsort_priority_queue.

Replication

• Per-engine mysql.gtid_slave_pos tables (MDEV-12179) — Implemented by Kristian Nielsen funded by Booking.com.

Data Type API

10.3 continues refactoring for the data type API started in 10.2, which will make it possible to have user data type plugins. This work is still in progress (see MDEV-4912 for the current status and subtasks). Most of the task in this category do not change the server behavior. Some tasks do have a visible effect.

Idle Transactions

Connections with idle transactions can be automatically killed after a specified time period by means of the idle_transaction_timeout, idle_readonly_transaction_timeout and idle_write_transaction_timeout system variables.

System Variables

For a list of all new variables, see System Variables Added in MariaDB 10.3 and Status Variables Added in MariaDB 10.3.

• New system variable gtid_pos_auto_engines.

• New system variable secure_timestamp for restricting the direct setting of a session timestamp (MDEV-15923)

• session variables tracking is enabled by default (MDEV-11825)

• Remove deprecated variables innodb_file_format, innodb_file_format_check, innodb_file_format_max and innodb_large_prefix.

• version_source_revision - permits seeing which version of the source was used for the build (MDEV-12583).

• Added bind_address as a system variable (MDEV-12542).

• The max value of the max_prepared_stmt_count system variable has been increased from 1048576 to 4294967295

• The proxy_protocol_networks variable can now be modified without restarting the server (MDEV-15501)

Security Vulnerabilities Fixed in MariaDB 10.3

For a complete list of security vulnerabilities (CVEs) fixed across all versions of MariaDB, see the Security Vulnerabilities Fixed in MariaDB page.

• CVE-2023-5157: MariaDB 10.3.36

• CVE-2022-47015: MariaDB 10.3.39

• CVE-2022-38791: MariaDB 10.3.36

• CVE-2022-32091: MariaDB 10.3.36

• CVE-2022-32088: MariaDB 10.3.35

• CVE-2022-32087: MariaDB 10.3.35

• CVE-2022-32085: MariaDB 10.3.35

• CVE-2022-32084: MariaDB 10.3.36

• CVE-2022-32083: MariaDB 10.3.35

• CVE-2022-31624: MariaDB 10.3.32

• CVE-2022-27458: MariaDB 10.3.35

• CVE-2022-27456: MariaDB 10.3.35

• CVE-2022-27452: MariaDB 10.3.35

• CVE-2022-27449: MariaDB 10.3.35

• CVE-2022-27448: MariaDB 10.3.35

• CVE-2022-27447: MariaDB 10.3.35

• CVE-2022-27445: MariaDB 10.3.35

• CVE-2022-27387: MariaDB 10.3.35

• CVE-2022-27386: MariaDB 10.3.35

• CVE-2022-27385: MariaDB 10.3.32

• CVE-2022-27384: MariaDB 10.3.35

• CVE-2022-27383: MariaDB 10.3.35

• CVE-2022-27381: MariaDB 10.3.35

• CVE-2022-27380: MariaDB 10.3.35

• CVE-2022-27379: MariaDB 10.3.35

• CVE-2022-27378: MariaDB 10.3.35

• CVE-2022-27377: MariaDB 10.3.35

• CVE-2022-27376: MariaDB 10.3.35

• CVE-2022-24052: MariaDB 10.3.33

• CVE-2022-24051: MariaDB 10.3.33

• CVE-2022-24050: MariaDB 10.3.33

• CVE-2022-24048: MariaDB 10.3.33

• CVE-2022-21595: MariaDB 10.3.33

• CVE-2022-21451: MariaDB 10.3.29

• CVE-2022-21427: MariaDB 10.3.35

• CVE-2022-0778: MariaDB 10.3.33

• CVE-2021-46669: MariaDB 10.3.35

• CVE-2021-46668: MariaDB 10.3.34

• CVE-2021-46667: MariaDB 10.3.32

• CVE-2021-46666: MariaDB 10.3.30

• CVE-2021-46665: MariaDB 10.3.34

• CVE-2021-46664: MariaDB 10.3.34

• CVE-2021-46663: MariaDB 10.3.34

• CVE-2021-46662: MariaDB 10.3.32

• CVE-2021-46661: MariaDB 10.3.34

• CVE-2021-46659: MariaDB 10.3.33

• CVE-2021-46658: MariaDB 10.3.31

• CVE-2021-46657: MariaDB 10.3.30

• CVE-2021-35604: MariaDB 10.3.32

• CVE-2021-27928: MariaDB 10.3.28

• CVE-2021-2389: MariaDB 10.3.31

• CVE-2021-2372: MariaDB 10.3.31

• CVE-2021-2194: MariaDB 10.3.26

• CVE-2021-2166: MariaDB 10.3.29

• CVE-2021-2154: MariaDB 10.3.29

• CVE-2021-2144: MariaDB 10.3.19

• CVE-2021-2022: MariaDB 10.3.24

• CVE-2021-2007: MariaDB 10.3.17

• CVE-2020-2922: MariaDB 10.3.17

• CVE-2020-28912: MariaDB 10.3.26

• CVE-2020-2814: MariaDB 10.3.23

• CVE-2020-2812: MariaDB 10.3.23

• CVE-2020-2780: MariaDB 10.3.19

• CVE-2020-2760: MariaDB 10.3.23

• CVE-2020-2752: MariaDB 10.3.23

• CVE-2020-2574: MariaDB 10.3.22

• CVE-2020-15180: MariaDB 10.3.25

• CVE-2020-14812: MariaDB 10.3.26

• CVE-2020-14789: MariaDB 10.3.26

• CVE-2020-14776: MariaDB 10.3.26

• CVE-2020-14765: MariaDB 10.3.26

• CVE-2020-13249: MariaDB 10.3.23

• CVE-2019-2974: MariaDB 10.3.19

• CVE-2019-2938: MariaDB 10.3.19

• CVE-2019-2805: MariaDB 10.3.17

• CVE-2019-2758: MariaDB 10.3.17

• CVE-2019-2740: MariaDB 10.3.17

• CVE-2019-2739: MariaDB 10.3.17

• CVE-2019-2737: MariaDB 10.3.17

• CVE-2019-2628: MariaDB 10.3.15

• CVE-2019-2627: MariaDB 10.3.15

• CVE-2019-2614: MariaDB 10.3.15

• CVE-2019-2537: MariaDB 10.3.13

• CVE-2019-2510: MariaDB 10.3.13

• CVE-2019-2503: MariaDB 10.3.10

• CVE-2018-3284: MariaDB 10.3.11

• CVE-2018-3282: MariaDB 10.3.11

• CVE-2018-3277: MariaDB 10.3.11

• CVE-2018-3251: MariaDB 10.3.11

• CVE-2018-3200: MariaDB 10.3.11

• CVE-2018-3185: MariaDB 10.3.11

• CVE-2018-3174: MariaDB 10.3.11

• CVE-2018-3173: MariaDB 10.3.11

• CVE-2018-3162: MariaDB 10.3.11

• CVE-2018-3156: MariaDB 10.3.11

• CVE-2018-3143: MariaDB 10.3.11

• CVE-2018-3066: MariaDB 10.3.9

• CVE-2018-3064: MariaDB 10.3.9

• CVE-2018-3063: MariaDB 10.3.9

• CVE-2018-3060: MariaDB 10.3.9

• CVE-2018-3058: MariaDB 10.3.9

• CVE-2018-25032: MariaDB 10.3.36

• CVE-2016-9843: MariaDB 10.3.11

Comparison with MySQL

• System Variable Differences Between MariaDB 10.3 and MySQL 8.0

• Function Differences Between MariaDB 10.3 and MySQL 8.0

• System Variable Differences Between MariaDB 10.3 and MySQL 5.7

• Function Differences Between MariaDB 10.3 and MySQL 5.7

List of All MariaDB 10.3 Releases

See Also

• Getting, Installing, and Upgrading MariaDB

• View the source tree

• 10.3 Features/fixes by vote

_{This page is licensed: CC BY-SA / Gnu FDL}

DownloadRelease NotesChangelogOverview of 10.3

Release date: 10 May 2023

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

MariaDB 10.3.39 is a Stable (GA) release.

MariaDB 10.3.39 is the last release of the MariaDB 10.3 release series.

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

Thanks, and enjoy MariaDB!

Notable Items

• As per the MariaDB Maintenance Policy, this will be the final release of MariaDB 10.3

Replication

• Fixed a deadlock on parallel slave involving full image Write event on the sequence engine (MDEV-29621)

Docker

• Add replication setup to containers contributed by Md Sahil (MDEV-29762)

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 inMDEV-14637.

Security

• Fixes for the following security vulnerabilities:

  • CVE-2022-47015

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

DownloadRelease NotesChangelogOverview of 10.3

Release date: 6 Feb 2023

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

MariaDB 10.3.38 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

• As mentioned in the 10.3.37 release notes, our Yum/DNF/Zypper repositories for Red Hat Enterprise Linux, CentOS, openSUSE, and SUSE are changing with this release to being signed with a new GPG key with SHA2 digest algorithms instead of SHA1. See this blog post and the GPG page for more details.

InnoDB

• Full-text index corruption with system versioning (MDEV-25004)

Replication

• Parallel slave applying in binlog order is corrected for admin class of commands including ANALYZE (MDEV-30323)

• Seconds_Behind_Master is now shown now more precisely at the slave applier start, including in the delayed mode (MDEV-29639)

• mysqlbinlog --verbose is made to show the type of compressed columns (MDEV-25277)

General

• Infinite sequence of recursive calls when processing embedded CTE (MDEV-30248)

• Crash with a query containing nested WINDOW clauses (MDEV-30052)

• Major performance regression with 10.6.11 (MDEV-29988)

Security

• Fixes for the following security vulnerabilities:

  • CVE-`-```

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.37Release NotesChangelogOverview of 10.3

Release date: 7 Nov 2022

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

MariaDB 10.3.37 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

SSL

• The server no longer tolerates incorrectly configured SSL (MDEV-29811). If you have enabled SSL in my.cnf but have not configured it properly (for example, a certificate file is missing), MariaDB used to silently disable SSL, leaving you under impression that everything was fine and connections were secure. Since this release, MariaDB will fail to start if SSL is enabled, but cannot be switched on.

Backup

• mariadb-backup --compress hangs (MDEV-29043)

InnoDB

• InnoDB unnecessarily extends data files (MDEV-13013)

• Adaptive hash index MDEV-27700, MDEV-29384

• MVCC and locking MDEV-29666, MDEV-27927

• Virtual columns MDEV-29299, MDEV-29753

JSON

• JSON_VALUE() does not parse NULL properties properly (MDEV-27151)

Replication

• minor correction in unsafe warning message (MDEV-28827)

• False replication error-stop of REVOKE PRIVILEGES from a non-existing user on primary (MDEV-28530) in combination with a filtering replica is corrected

• SET DEFAULT ROLE replication is mended on a replica that filters system tables (MDEV-28294)

Repositories

• Beginning with the next release (Q1 2023), our Yum, DNF, and Zypper repositories for Red Hat, Fedora, and SUSE will be migrated to being signed with a new GPG key. The key we are migrating to is the same one we already use for our Debian and Ubuntu Repositories.

  • The short Key ID is: 0xC74CD1D8

  • The long Key ID is: 0xF1656F24C74CD1D8

  • The full fingerprint of the key is: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8

  • The key can be imported now in preparation for this change using the following command:

sudo rpm --import https://supplychain.mariadb.com/MariaDB-Server-GPG-KEY

Docker Official Image

The following changes have been made to the docker.io/library/mariadb container image.

• The number of gpg packages has been removed, leaving enough to apt-get update, but dirmngr that would fetch keys has been removed. (inspired by issue #469)

• The environment variable LANG=C.UTF-8 has been added for those that exec into containers and copy paste UTF8 characters (fixes issue #468).

• Adds OCI labels to image (fixes issue 436 and users need for version)

• MariaDB config: skip-host-cache and skip-name-resolve moved to /etc/mysql/mariadb.conf.d/05-skipcache.cnf

Security

• Fixes for the following security vulnerabilities:

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.36Release NotesChangelogOverview 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 ofMariaDB 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

• CONNECT Engine now supports INSERT IGNORE with Mysql Table type (MDEV-27766)

mysql Client

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

General

• Crash in JSON_EXTRACT (MDEV-29188)

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Debian 10 "Buster" for ppc64el

Security

• Fixes for the following security vulnerabilities:

  • CVE-2023-5157

  • CVE-2018-25032

  • CVE-2022-32091

  • CVE-2022-32084

  • CVE-2022-38791

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.35Release NotesChangelogOverview of 10.3

Release date: 20 May 2022

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

MariaDB 10.3.35 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_disallow_writes removed (MDEV-25975)

• InnoDB gap locking fixes (MDEV-20605, MDEV-28422)

Replication

• Binlogs disappear after rsync IST (MDEV-28583)

• master crash is eliminated in compressed semisync replication protocol with packet counting amendment (MDEV-25580)

• OPTIMIZE on a sequence does not cause counterfactual ER_BINLOG_UNSAFE_STATEMENT anymore (MDEV-24617)

• Automatically generated Gtid_log_list_event is made to recognize within replication event group as a formal member (MDEV-28550)

• Replication unsafe INSERT .. ON DUPLICATE KEY UPDATE using two or more unique key values at a time with MIXED format binlogging is corrected (MDEV-28310)

• Replication unsafe INSERT .. ON DUPLICATE KEY UPDATE stops issuing unnecessary "Unsafe statement" with MIXED binlog format (MDEV-21810)

• Incomplete replication event groups are detected to error out by the slave IO thread (MDEV-27697)

• mysqlbinlog --stop-never --raw now flushes the result file to disk after each processed event so the file can be listed with the actual bytes (MDEV-14608)

Backup

• Incorrect binlogs after Galera SST using rsync and MariaDB Backup (MDEV-27524)

• MariaDB Backup does not detect multi-source replication slave (MDEV-21037)

• Useless warning "InnoDB: Allocated tablespace ID for , old maximum was 0" during backup stage (MDEV-27343)

• MariaDB Backup prepare fails for incrementals if a new schema is created after full backup is taken (MDEV-28446)

Optimizer

• ANALYZE FORMAT=JSON fields are incorrect for UNION ALL queries (MDEV-27699)

• Subquery in an UPDATE query uses full scan instead of range (MDEV-22377)

• Assertion `item1->type() == Item::FIELD_ITEM ... (MDEV-19398)

• Server crashes in Expression_cache_tracker::fetch_current_stats (MDEV-28268)

• MariaDB server crash at Item_subselect::init_expr_cache_tracker (MDEV-26164, MDEV-26047)

• Crash with union of my_decimal type in ORDER BY clause (MDEV-25994)

• SIGSEGV in st_join_table::cleanup (MDEV-24560)

• Assertion `!eliminated' failed in Item_subselect::exec (MDEV-28437)

General

• For RHEL/CentOS 7, non x86_64 architectures are no longer supported upstream and so our support will also be dropped with this release

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Debian 9 "Stretch"

Security

• Fixes for the following security vulnerabilities:

  • CVE-2021-46669

  • CVE-2022-21427

  • CVE-2022-27376

  • CVE-2022-27377

  • CVE-2022-27378

  • CVE-2022-27379

  • CVE-2022-27380

  • CVE-2022-27381

  • CVE-2022-27383

  • CVE-2022-27384

  • CVE-2022-27386

  • CVE-2022-27387

  • CVE-2022-27445

  • CVE-2022-27447

  • CVE-2022-27448

  • CVE-2022-27449

  • CVE-2022-27452

  • CVE-2022-27456

  • CVE-2022-27458

  • CVE-2022-32087

  • CVE-2022-32085

  • CVE-2022-32083

  • CVE-2022-32088

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.34Release NotesChangelogOverview of 10.3

Release date: 12 Feb 2022

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

MariaDB 10.3.34 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

• This release fixes a blocking problem with the MariaDB 10.3.33 release when manually running mariadb-upgrade. (MDEV-27789)

• See MariaDB 10.3.33 for other changes since the previous release.

Security

• Fixes for the following security vulnerabilities:

  • CVE-2021-46665

  • CVE-2021-46664

  • CVE-2021-46661

  • CVE-2021-46668

  • CVE-2021-46663

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.33Release NotesChangelogOverview of 10.3

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.

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

MariaDB 10.3.33 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

• --skip-symbolic-links does not disallow .isl file creation (MDEV-26870)

Galera

• Galera updated to 25.3.35(galera 25.3.35 Release Notes)

• Galera SST scripts should use ssl_capath (not ssl_ca) for CA directory (MDEV-27181)

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)

Packaging & Misc

• prohibition running two upgrades in parallel (MDEV-27068, MDEV-27107, MDEV-27279)

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for CentOS 8

• mariadb_repo_setup script updated to version 2022-02-08, with the following fixes and enhancements:

  • Default location of the script has been moved to: mariadb_repo_setup (old location is deprecated, but still works)

  • The GPG keyring file, used with Debian and Ubuntu repositories, has moved to: mariadb-keyring-2019.gpg and the checksum for the file can be found at: mariadb-keyring-2019.gpg.sha256

  • Support for RHEL and SLES aarch64 repositories added

  • New function added to verify that the MariaDB Server version, if specified on the command line, follows the correct naming and that a corresponding repository actually exists.

  • Fixed repository pinning for Ubuntu and Debian repositories

  • MariaDB Server 10.7 is now the default server version

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)

Security

• Fixes for the following security vulnerabilities:

  • CVE-2022-24052

  • CVE-2022-24051

  • CVE-2022-24050

  • CVE-2022-24048

  • CVE-2021-46659

  • CVE-2022-0778

  • CVE-2022-21595

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.32Release NotesChangelogOverview of 10.3

Release date: 8 Nov 2021

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

MariaDB 10.3.32 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

Galera

• Fix for WSREP: invalid state ROLLED_BACK (FATAL) (MDEV-25114)

InnoDB

• ALTER TABLE…IMPORT TABLESPACE fixes (MDEV-20931, MDEV-26131)

• innodb_undo_log_truncate fixes (MDEV-26450, MDEV-26672, MDEV-26864)

Replication

• Memory hogging on slave by ROW event applier is eliminated (MDEV-26712)

• mysql --binary-mode now properly handles \\0 in data (MDEV-25444)

• Missed statement rollback in case transaction drops or create temporary table is corrected (MDEV-26833)

Packaging & Misc

• Session tracking flag in OK_PACKET (MDEV-26868)

• Some views force server (and mysqldump) to generate invalid SQL for their definitions (MDEV-26299)

Security

• Fixes for the following security vulnerabilities:

  • CVE-2021-35604

  • CVE-2021-46667

  • CVE-2021-46662

  • CVE-2022-27385

  • CVE-2022-27385

  • CVE-2022-31624

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.31Release NotesChangelogOverview of 10.3

Release date: 6 Aug 2021

Warning: This version can cause InnoDB file corruption on FreeBSD and on AIX. If you are using AIX, please, stick to an earlier release, or upgrade to a more recent release. If you are using FreeBSD, upgrade to the bugfix release (the version ends with _1) of the mariadb-server from the Ports Collection. See MDEV-26537.

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

MariaDB 10.3.31 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 no longer acquires advisory file locks by default (MDEV-24393)

• Encryption: Automatically disable key rotation checks for file_key_management plugin (MDEV-14180)

• Some fixes from MySQL 5.7.35 (MDEV-26205)

Optimizer

• A query that uses ORDER BY .. LIMIT clause and "Range checked for each record optimization" could produce incorrect results under some circumstances (MDEV-25858)

• Queries that have more than 32 equality conditions comparing columns of different tables ("tableX.colX=tableY.colY) could cause a stack overrun in the query optimizer (MDEV-17783, MDEV-23937)

• "Condition pushdown into derived table" optimization cannot be applied if the expression being pushed refers to a derived table column which is computed from expression that has a stored function call, @session variable reference, or other similar construct. The fix for MDEV-25969 makes it so that only the problematic part of the condition is not pushed. The rest of the condition is now pushed. (MDEV-25969)

• A query with window function on the left side of the subquery could cause a crash. (MDEV-25630)

• Wrong result selecting from simple view with LIMIT and ORDER BY Queries with views/derived table/CTEs that have this form: "(SELECT ... LIMIT ) ORDER BY ...>" could produce wrong results (MDEV-25679)

Packaging & Misc

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Ubuntu 20.10 Groovy

• Galera updated to 25.3.34

Security

• Fixes for the following security vulnerabilities:

  • CVE-2021-2372

  • CVE-2021-2389

  • CVE-2021-46658

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 inMDEV-14637. MongoDB protocol support files for the CONNECT engine are missing in this release. If you want to use CONNECT engine with MongoDB, you need to downloadMongo2.jar or Mongo3.jar and put a path to this file into the connect_class_path in the my.cnf.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.30Release NotesChangelogOverview of 10.3

Release date: 23 Jun 2021

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

MariaDB 10.3.30 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

This version of MariaDB is being released now to fix the following two regressions:

• Table alias from previous statement interferes later commands (MDEV-25672)

• Join using derived with aggregation returns incorrect results (MDEV-25714)

In addition to the above, this release also contains the following fixes:

InnoDB

• Change buffer entries are lost on InnoDB restart (MDEV-25869)

• InnoDB spatial indexes miss large geometry fields after MDEV-25459 (MDEV-25758)

• Double free of transaction during truncate operation (MDEV-25663)

• Double free of table when inplace alter FTS add index fails (MDEV-25721)

• Potential hang in purge for virtual columns (MDEV-25664)

• Change buffer entries for secondary indexes are lost on InnoDB restart (MDEV-25869)

Replication

• Do not replicate killed multi-table OPTIMIZE TABLE when the signal arrives before any table has been processed (MDEV-22530)

• Fix optistic parallel applier to not deadlock on admin commands OPTIMIZE, REPAIR, and ANALYZE (MDEV-17515)

• Backport MDEV-20821 parallel slave server shutdown hang (MDEV-22370)

Security

• Fixes for the following security vulnerabilities:

  • CVE-2021-46666

  • CVE-2021-46657

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 inMDEV-14637. MongoDB protocol support files for the CONNECT engine are missing in this release. If you want to use CONNECT engine with MongoDB, you need to downloadMongo2.jar or Mongo3.jar and put a path to this file into the connect_class_path in the my.cnf.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.29Release NotesChangelogOverview of 10.3

Release date: 7 May 2021

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

MariaDB 10.3.29 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 Changes

• ST_DISTANCE_SPHERE for calculating the spherical distance between two geometries (point or multipoint) on a sphere (MDEV-13467)

• Crash with invalid multi-table update of view in 2nd execution of SP (MDEV-24823)

• Incorrect name resolution for subqueries in ON expressions (MDEV-25362)

• Complex query in Store procedure corrupts results (MDEV-25182)

• DELETE HISTORY may delete current data on system-versioned table (MDEV-25468)

• Crashes with nested table value constructors (MDEV-22786)

mariadb-backup

• RENAME TABLE causes "Ignoring data file" messages (MDEV-25568)

InnoDB

• Deprecated the *innodb and *none options in innodb_checksum_algorithm (MDEV-25106)

• MVCC read from index on CHAR or VARCHAR wrongly omits rows (MDEV-25459)

• Race conditions in persistent statistics (MDEV-10682, MDEV-18802, MDEV-25051)

• Sequence created by one connection remains invisible to another (MDEV-24545)

Replication

• Replication Heartbeat event was uncapable to cary 4GB+ offsets (MDEV-16146)

• FLUSH LOGS race against Binlog checkpoint event creation (MDEV-24526)

• slave_compressed_protocol did not work correctly with semi-sync (MDEV-24773)

Galera

• Galera updated to 25.3.33

• SET PASSWORD command fail with wsrep api (MDEV-25258)

• Long BF log wait turns on InnoDB Monitor output without telling, never turns it off (MDEV-25319)

Audit Plugin

• The QUERY_DDL server_audit_events setting now logs CREATE/DROP [PROCEDURE / FUNCTION / USER] statements. See MariaDB Audit Plugin - Log Settings. (MDEV-23457)

Packaging & Misc

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Ubuntu 16.04 Xenial

Security

• Fixes for the following security vulnerabilities:

  • CVE-2021-2166

  • CVE-2021-2154

  • CVE-2022-21451

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 inMDEV-14637. MongoDB protocol support files for the CONNECT engine are missing in this release. If you want to use CONNECT engine with MongoDB, you need to downloadMongo2.jar or Mongo3.jar and put a path to this file into the connect_class_path in the my.cnf.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.28Release NotesChangelogOverview of 10.3

Release date: 22 Feb 2021

Last month long-time MariaDB VP of Engineering, Rasmus Johansson, passed due to complications from cancer. His loss has been felt keenly by the whole MariaDB team. Our thoughts are with his family during this difficult time and this release is dedicated to his memory.

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

MariaDB 10.3.28 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 Changes

InnoDB

• MDEV-24188 - Hang in buf_page_create() after reusing a previously freed page

• MDEV-24275 - InnoDB persistent stats analyze forces full scan forcing lock crash

• MDEV-24449 - Corruption of system tablespace or last recovered page

Galera

• Galera updated to 25.3.32

• MDEV-23328 - Server hang due to Galera lock conflict resolution

• MDEV-23851 - BF-BF Conflict issue because of UK GAP locks

• MDEV-20717 - Plugin system variables and activation options can break mysqld --wsrep_recover

• MDEV-25179 - wsrep_provider and wsrep_notify_cmd system variables are now read-only

Replication

• MDEV-8134 - relay-log is corrected to rotate past 999999

• MDEV-23033 - fixed slave applier for row-based events with FK constraints on virtual columns

• MDEV-4633 - Relay_Log_Space of Show-Slave-Status is made thread-safe

• MDEV-10272 - add master host/port info to slave thread exit messages

Misc

• MDEV-24122 - anomalies in mysql.user tables on previously 5.7 MySQL versions corrected

• MDEV-23630 - mysqldump --system option

• Fixes for the following security vulnerabilities:

  • CVE-2021-27928

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.27Release NotesChangelogOverview of 10.3

Release date: 11 Nov 2020

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

MariaDB 10.3.27 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 Changes

• Out-of-cycle release to fix regressions in MariaDB 10.3.26

• Follow up to MDEV-19838 to alter protocol checks to support the following implementations (which add garbage to the end of some packets):

  • PHP PDO (all versions) (MDEV-24121)

  • mysqlnd (from PHP < 7.3) (MDEV-24121)

  • mysql-connector-python (all versions) (MDEV-24134)

  • and mysql-connector-java (all versions)

• The query optimizer consumed a lot of memory when handling construct in form of key_column [NOT] IN (large-list-of constants) (MDEV-24117)

• Fixes for the following security vulnerabilities:

  • CVE--``#

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.26Release NotesChangelogOverview of 10.3

Release date: 3 Nov 2020

MariaDB 10.3 is the previous stable series of MariaDB, 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.26 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 Changes

• Set the default value of innodb_log_optimize_ddl to OFF by default (MDEV-23720)

• BLACKHOLE Storage Engine maximum index size increased from 1000 to 3500 bytes (MDEV-24017)

• Calculating (auto rounding) issue (MDEV-23702)

• Temporary tables can no longer overwrite existing files. Instead an error is returned should a conflict occur (MDEV-23569)

• Binlog checksum verification at recovery time (MDEV-23832)

• Verbose print-out of Geometry types by mysqlbinlog (MDEV-22330)

• SHOW BINLOG EVENTS from validates when binlog checksummed (MDEV-21839)

• Freeing memory of replicate_do_table (MDEV-23534)

• Corrected verbose mysqlbinlog output for multi-record Rows-log-event (MDEV-16372)

• SET GLOBAL replicate_do_db = DEFAULT no longer causes crash (MDEV-20744)

• User killed queries that were running an index condition pushdown in InnoDB will now return an error (MDEV-23938)

• Wrong direxec param data caused crash; Numerous fixes about Mac builds (by Dmitri Shulga) (MDEV-19838)

• server_audit plugin now logs proxy users (MDEV-19443)

• Crash on SELECT on a table with indexed virtual columns (MDEV-18366)

• InnoDB updated to 5.7.32 (MDEV-23989)

• Bug fixes related to adaptive hash index (MDEV-23452, MDEV-23370)

• Fixed a bug in the recovery of encrypted tables (MDEV-23456)

• Fixed a race condition in MVCC reads (MDEV-22924)

• ALTER TABLE fixes (MDEV-22277, MDEV-22939, MDEV-23685, MDEV-23722)

• Diskspace not reused for BLOB in data file (MDEV-23072)

• InnoDB: Failing assertion: !space->referenced() (MDEV-23651)

• SIGSEGV in maria_create() because of double free (MDEV-23222)

• CREATE TEMPORARY TABLE .. LIKE (system versioned table) returns error if unique index is defined in the table (MDEV-23968)

• Error upon querying the view, that selecting from versioned table with partitions (MDEV-23779)

• CREATE .. SELECT wrong result on join versioned table (MDEV-23799)

• Fixed a crash with the NTH_VALUE function (MDEV-15180)

• Computing certain window functions on a server started with --encrypt-tmp_files=ON could cause a wrong query result or crash (MDEV-23867)

• A query with a certain form of WHERE clause over a table with multiple indexes could pick a less efficient range plan (MDEV-23811)

• Fixed a memory leak for correlated subqueries with ROLLUP (MDEV-17066)

Galera

• Galera wsrep library updated to 25.3.31

• Fixed galera got stuck after flush tables (MDEV-22707)

• Fixed data loss on rolling upgrade between 10.3 and 10.4 (MDEV-22723)

• IPv6 SST handling improved (MDEV-21770, MDEV-23576, MDEV-23580, MDEV-23581, MDEV-23574)

• Fixed SIGSEGV in lock_rec_unlock (MDEV-23101)

• Fixed replication of timezone if only 1 timezone is loaded (MDEV-22626)

• Fixed replication of CREATE OR REPLACE TRIGGER (MDEV-21578)

• Fixed SST FLUSH TABLES WITH READ LOCK timeout (MDEV-22543)

Notes

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for CentOS/RHEL 6 and Fedora 31

• Packages for Ubuntu 20.10 "Groovy Gorilla" added

• Packages for Debian 10 "buster" arm64 and ppc64el added

• Packages for Debian 9 "stretch" arm64 added

• Fixes for the following security vulnerabilities:

  • CVE-2020-14812

  • CVE-2020-14765

  • CVE-2020-14776

  • CVE-2020-14789

  • CVE-2020-28912 (MDEV-24040)

  • CVE-2021-2194 (MDEV-18366)

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Download 10.3.25Release NotesChangelogOverview of 10.3

Release date: 7 Oct 2020

MariaDB 10.3 is the previous stable series of MariaDB, 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.25 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 Changes

• Fixes for the following security vulnerabilities:

  • CVE-2020-15180

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

DownloadRelease NotesChangelogOverview of 10.3

Release date: 10 Aug 2020

MariaDB 10.3 is the previous stable series of MariaDB, 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.24 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 Changes

Variables

• Limit innodb_encryption_threads to 255 (MDEV-22258).

• Minimum value of max_sort_length raised to 8 (previously 4) so fixed size data types like DOUBLE and BIGINT are not truncated for lower values of max_sort_length (MDEV-22715).

InnoDB

• Fixed corruption in delete buffering (MDEV-22497)

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

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

• Minor fixes related to encryption and FULLTEXT INDEX

• Dropping the adaptive hash index may cause DDL to lock up InnoDB (MDEV-22456)

• innodb_log_optimize_ddl=OFF is not crash safe (MDEV-21347)

• Mariadb service won't shutdown when it's running and the OS datetime updated backwards (MDEV-17481)

• Doublewrite recovery can corrupt data pages (MDEV-11799)

• Fixed race conditions related to buffer pool resizing

• ALTER TABLE fixes (MDEV-22637, MDEV-23244)

• Crash recovery fixes (MDEV-21347, MDEV-23190, MDEV-11799)

Replication

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

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

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

• Correct 'relay-log.info' updating by concurrent parallel workers (MDEV-22806)

• Eliminate deadlock involving parallel workers, STOP SLAVE and FLUSH TABLES WITH READ LOCK (MDEV-23089)

• Correct master-slave automatic reconnection by slave to always pass through all steps of the initial connect. Specifically, do not skip master notification about slave binlog checksum awareness (MDEV-14203)

• Refine mysqlbinlog output to print out START TRANSACTION at Gtid_log_event processing which satisfies clients that submit the output with sql_mode=oracle (MDEV-23108)

• Replication aborts with ER_SLAVE_CONVERSION_FAILED upon CREATE ... SELECT in ORACLE mode (MDEV-19632)

Optimizer

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

• 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 (MDEV-22665)

• LATERAL DERIVED is not clearly visible in EXPLAIN FORMAT=JSON, make LATERAL DERIVED tables visible in EXPLAIN FORMAT=JSON output (MDEV-17568)

• Crash on WITH RECURSIVE large query (MDEV-22748)

• Crash with Prepared Statement with a '?' parameter inside a re-used CTE (MDEV-22779)

Other

• div_precision_increment 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 div_precision_increment (MDEV-19232)

• mariadb_schema data type qualifier allowing MariaDB native date types in an SQL_MODE that has conflicting data type translations.

• MariaDB could crash after changing the query_cache size (MDEV-5924)

• Errors and SIGSEGV on CREATE TABLE w/ various charsets (MDEV-22111)

• Crash in CREATE TABLE AS SELECT when the precision of returning type = 0 (MDEV-22502)

• XA: Reject DDL operations between PREPARE and COMMIT (MDEV-22420)

• Stop mariadb-backup --prepare on errors during innodb redo log applying (MDEV-22354)

• Server crashes in mysql_alter_table upon adding a non-null date column under NO_ZERO_DATE with ALGORITHM=INPLACE (MDEV-18042)

• Can't uninstall plugin if the library file doesn't exist (MDEV-21258)

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Ubuntu 19.10 Eoan and Fedora 30

• Fixes for the following security vulnerabilities:

  • CVE-2021-2022

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

DownloadRelease NotesChangelogOverview of 10.3

Release date: 12 May 2020

MariaDB 10.3 is the previous stable series of MariaDB, 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.23 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 Changes

Events

• Fixed issue that, from MariaDB 10.3.19, disabled all events created by a server with a different server_id. Note that the fix does not re-enable affected events. (MDEV-21758)

Privileges

• SHOW PRIVILEGES now correctly lists the Delete history privilege, rather than displaying it as Delete versioning rows. (MDEV-20382)

Other

• HeidiSQL updated to 11.0 (MDEV-22032)

• Introduce a file format constraint to ALTER TABLE. See innodb_instant_alter_column_allowed (MDEV-20590)

• ALTER TABLE, FORCE all partition to rebuild if any one of the partition does rebuild (MDEV-21832)

• ALTER TABLE, InnoDB aborts while adding instant column for discarded tablespace (MDEV-22446)

• Optimizer, Wrong query results with optimizer_switch="split_materialized=on" (MDEV-21614)

• SHOW GRANTS does not quote role names properly (MDEV-20076)

• Paritioning INSERT chooses wrong partition for RANGE partitioning by DECIMAL column (MDEV-21195)

• mariadb-backup does not honor ignore_db_dirs from server config (MDEV-19347)

• mariadb-backup --ftwrl-wait-timeout never times out on explicit lock (MDEV-20230)

• FULLTEXT INDEX, Assertion ``!table->fts->in_queue' failed in fts_optimize_remove_table` (MDEV-21550)

• Wrong estimate of affected BLOB columns in update of PRIMARY KEY (MDEV-22384)

• Duplicate key value is silently truncated to 64 characters in print_keydup_error (MDEV-20604)

• Session tracking returns incorrectly long tracking data (MDEV-22504)

• Add pam_user_map.so file to binary tarball package (MDEV-21913)

• Running out of file descriptors and eventual crash (MDEV-18027)

• mysql_upgrade is made aware of the upstream slave tables to issue warnings when that takes place (MDEV-10047)

• Corruption for SET GLOBAL innodb_ string variables (MDEV-22393)

• wsrep performance optimization (MDEV-7962)

• mysqldump parameter, --ignore-table-data, added (MDEV-22037)

• Server can fail while replicating conditional comments (Bug#28388217)

• Galera wsrep library updated to 25.3.29

• Added the xml-report option to mysql-test-run (MDEV-22176)

• Packages and repositories for Ubuntu 20.04 "focal" added

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Debian 8 "Jessie"

• Fixes for the following security vulnerabilities:

  • CVE-2020-2752

  • CVE-2020-2812

  • CVE-2020-2814

  • CVE-2020-2760

  • CVE-2020-13249

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 inMDEV-14637.

Changelog

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

Contributors

For a full list of contributors to MariaDB 10.3.23, see the MariaDB Foundation release announcement. Thanks, and enjoy MariaDB!>

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Note that this version contains an issue that disabled all events created by a server with a different server_id. See MDEV-21758 for details.

DownloadRelease NotesChangelogOverview of 10.3

Release date: 28 Jan 2020

MariaDB 10.3 is the previous stable series of MariaDB, 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.22 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 Changes

General

• MDEV-21337: fix aligned_malloc()

• MDEV-21343: Threadpool/Unix- wait_begin() function does not wake/create threa ds, when it should

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Ubuntu 19.04 Disco

mariadb-backup

• MDEV-21255: Deadlock of parallel slave and mariadb-backup (with failed log copy thread)

InnoDB

• MDEV-20950: Reduce size of record offsets

• MDEV-19176: Reduce the memory usage during recovery

• MDEV-21429: TRUNCATE and OPTIMIZE are being refused due to "row size too large"

• MDEV-21500: Server hang when using simulated AIO

• MDEV-21509: Possible hang during purge of history, or rollback

• MDEV-21511: Wrong estimate of affected BLOB columns in update

• MDEV-21512: InnoDB may hang due to SPATIAL INDEX

• MDEV-21513: Avoid some crashes in ALTER TABLE...IMPORT TABLESPACE

• MDEV-18865: Assertion `t->first->versioned_by_id()' failed in innodb_prepare_commit_versioned

Aria

• MDEV-14183: aria_pack segfaults in compress_maria_file

Optimizer

• MDEV-21318: Wrong results with window functions and implicit grouping

• MDEV-16579: Wrong result of query using DISTINCT COUNT() OVER ()

• MDEV-21383: Possible range plan is not used under certain conditions

Replication

• MDEV-18046: Crashes caused by random values to the offset option of SHOW BINLOG EVENT offset command

• MDEV-19376: Semisync Master could crash when it executed RESET MASTER and a replica reconnects using GTID protocol

Security

• Fixes for the following security vulnerabilities:

  • CVE-2020-2574

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Note that this version contains an issue that disabled all events created by a server with a different server_id. See MDEV-21758 for details.

DownloadRelease NotesChangelogOverview of 10.3

Release date: 11 Dec 2019

MariaDB 10.3 is the previous stable series of MariaDB, 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.21 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 Changes

General

• MDEV-13492: SEC_E_INVALID_TOKEN when server sends large message during SSL handshake

mariadb-backup

• MDEV-18310: Aria engine: Undo phase failed from incremental backup

InnoDB

• MDEV-20949: Stop issuing 'row size' error on DML

• MDEV-20832: Don't print "row size too large" warnings in error log if innodb_strict_mode=OFF and log_warnings<=2

• MDEV-21024: Remove redundant writes to the redo log

• MDEV-21069: Crash on DROP TABLE if the data file is corrupted

• some cleanup of AIO code, to better report errors

• MDEV-20611: MRR scan over partitioned InnoDB table produces "Out of memory" error

• MDEV-21088: Table cannot be loaded after instant ADD/DROP COLUMN

• MDEV-21045: heap-use-after-poison in ADD PRIMARY KEY after instant ADD COLUMN

• MDEV-21172: Memory leak after failed ADD PRIMARY KEY

• MDEV-21158: trx_undo_seg_free() is never redo-logged

Optimizer

• MDEV-21044: Wrong result when using a smaller size for sort buffer

• MDEV-20611: MRR scan over partitioned InnoDB table produces "Out of memory" error

Replication

• MDEV-19376: Repl_semi_sync_master::commit_trx assertion failure

Versioning

• MDEV-18929: 2nd execution of SP does not detect ER_VERS_NOT_VERSIONED

• MDEV-21011: Table corruption reported for versioned partitioned table after DELETE

Misc

• Packages for Fedora 31 have been added in this release

• As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.3 for Fedora 29

• Fixes for the following security vulnerabilities:

  • CVE-`-```

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

Note that this version contains an issue that disabled all events created by a server with a different server_id. See MDEV-21758 for details.

DownloadRelease NotesChangelogOverview of 10.3

Release date: 8 Nov 2019

MariaDB 10.3 is the previous stable series of MariaDB, 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.20 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 Changes

• MDEV-20987: InnoDB fails to start when FTS table has FK relation

• See also the release notes for MariaDB 10.3.19 for additional items of note

• Fixes for the following security vulnerabilities:

  • CVE-`-```

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

After an upgrade MariaDB Server can crash if InnoDB tables exist with a FULLTEXT INDEX and a FOREIGN KEY constraint attached to them. We got reports that the crash already will be encountered on startup, but a crash is also possible at a later stage. See MDEV-20987 for more details.Do not download or use this release.

DownloadRelease NotesChangelogOverview of 10.3

Alternate download from mariadb.org

Release date: 5 Nov 2019

MariaDB 10.3 is the previous stable series of MariaDB, 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.19 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 Changes

• MDEV-20864: Debug-only option innodb_change_buffer_dump for dumping the contents of the InnoDB change buffer to the server error log at startup.

• mariadb-backup:

  • MDEV-18438: mbstream recreates xtrabackup_info on same directory as backup file

  • MDEV-20703: mariadb-backup creates binlog files in server binlog directory on --prepare --export step

• Read-only replicas

  • Issues related to read only replicas are fixed:

  • CREATE, DROP, ALTER, INSERT and DELETE of temporary tables are not logged to binary log, even in statement or mixed mode. With earlier MariaDB versions, one can avoid the problem with temporary tables by using binlog_format=ROW in which cases temporary tables are never logged.

  • Changes to temporary tables created during read_only will not be logged even after read_only mode is disabled (for example if the replica is promoted to a primary).

  • The Admin statements ANALYZE, OPTIMIZE and REPAIR will not be logged to the binary log under read-only.

• FULLTEXT INDEX:

  • MDEV-19647: Server hangs after dropping full text indexes and restart

  • MDEV-19529: InnoDB hang on DROP FULLTEXT INDEX

  • MDEV-19073: FTS row mismatch after crash recovery

  • MDEV-20621: FULLTEXT INDEX activity causes InnoDB hang

• MDEV-20927: Duplicate key with auto increment

• ALTER TABLE:

  • MDEV-20799: DROP Virtual Column crash

  • MDEV-20852: BtrBulk is unnecessarily holding dict_index_t::lock

• System-Versioned Tables:

  • MDEV-16210: FK constraints on versioned tables use historical rows, which may cause constraint violation

  • MDEV-20812: Unexpected ER_ROW_IS_REFERENCED_2 or server crash in row_ins_foreign_report_err upon DELETE from versioned table with FK

• Galera wsrep library updated to 25.3.28

• Packages for Ubuntu 19.10 Eoan have been added in this release

• Fixes for the following security vulnerabilities:

  • CVE-2019-2974

  • CVE-2019-2938

  • CVE-2020-2780

  • CVE-2021-2144

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

DownloadRelease NotesChangelogOverview of 10.3

Release date: 11 Sep 2019

MariaDB 10.3 is the previous stable series of MariaDB, 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.18 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 Changes

• Connect updated to Connect 1.06.0010

• MDEV-20066: This bug could cause a table to become corrupt if a column was added instantly

• MDEV-15326: A race condition in InnoDB transaction commit that affects record locking was fixed

• MDEV-17187: Table doesn't exist in engine after ALTER of FOREIGN KEY

• MDEV-20301: InnoDB's MVCC has O(N^2) behaviors

• MDEV-18128: Simplify .ibd file creation

• MDEV-20060: Failing assertion: srv_log_file_size <= 512ULL << 30 while preparing backup

• MDEV-20247: Replication hangs with "preparing" and never starts

• MDEV-17614: Remove unnecessary locking for INSERT...ON DUPLICATE KEY UPDATE

• MDEV-20311: row_ins_step accesses uninitialized memory

• MDEV-19947: Repositories for RHEL 8 ppc64le added

• Fixes for the following security vulnerabilities:

  • CVE-`-```

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 inMDEV-14637.

Changelog

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

Contributors

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

DownloadRelease NotesChangelogOverview of 10.3

Release date: 31 Jul 2019

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