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
()
Syntax / General Features
(also known as AS OF) ()
() — GSoC 2017 project by Galina Shalygina
() — GSoC 2017 project by Galina Shalygina
Compatibility
As a result of implementing Table Value Constructors, the has been renamed to VALUE() ()
When running with , the server now understands a subset of Oracle's PL/SQL language instead of the traditional MariaDB syntax for stored routines. See , and to know the current status.
New , EMPTY_STRING_IS_NULL.
Compression
() — Tencent Game DBA Team, developed by willhan, also thanks to AliSQL.
On Linux, shrink the core dumps by omitting the InnoDB buffer pool ()
Encryption
Temporary files created by merge sort and row log are encrypted if is set to 1, regardless of whether the table encrypted or not ().
Optimizer/Performance
Condition pushdown through PARTITION BY clause of ()
New was introduced.
Numerous performance improvements for high-concurrency load
Storage Engines
InnoDB
now has a new mode, 3, which skips the rollback of connected transactions ()
Spider
The 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.
Most of the features were done as part of .
OQGRAPH
now supports the "leaves" algorithm () — contribution by Heinz Wiesinger
Partition Engine
Numerous improvements for the partition engine () — contribution by Kentoku Shiba
Full text support.
Multi-range-read (Gives better performance when handling multiple ranges).
Information Schema
The Information Schema is optimized to use much less memory when selecting from or any other table with many or columns ()
The now displays info in the EXTRA column -
Logging
Disable logging of certain statements to the or the with the and system variables.
A new option to , filsort_priority_queue.
Replication
Per-engine mysql.gtid_slave_pos tables () — 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 for the current status and subtasks). Most of the task in this category do not change the server behavior. Some tasks do have a .
Idle Transactions
Connections with idle transactions can be automatically killed after a specified time period by means of the , and system variables.
System Variables
For a list of all new variables, see and .
New system variable .
New system variable for restricting the direct setting of a session timestamp ()
is enabled by default ()
Security Vulnerabilities Fixed in
For a complete list of security vulnerabilities (CVEs) fixed across all
versions of MariaDB, see the
page.
:
:
:
Comparison with MySQL
List of All Releases
Date
Release
Status
Release Notes
Changelog
See Also
Be notified of new MariaDB Server releases automatically by 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 page.
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):
New SIMULTANEOUS_ASSIGNMENT to make the SET part of the statement evaluate all assignments simultaneously, not left-to-right.
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 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)