Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
MariaDB 10.1 Series Release Notes
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
Download 10.1.47Release NotesChangelogOverview of 10.1
Release date: 7 Oct 2020
MariaDB 10.1 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.47 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.47 with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.47, see the MariaDB Foundation release announcement.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 7 Nov 2016
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.19 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 5.6.33-79.0
updated to 5.6.33-79.0
Packages for Ubuntu 16.10 Yakkety added. Use the Repository Configuration Tool to add the MariaDB Ubuntu repository to your system.
Fixes for the following :
CVE-2016-5483 (re-issued later as CVE-2017-3600)
For a complete list of changes made in MariaDB 10.1.19, with links to detailed information on each push, see the changelog.
Release date: 3 Nov 2020
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 25.3.31
maximum index size increased from 1000 to 3500 bytes ()
issue ()
Temporary tables can no longer overwrite existing files. Instead an error is returned should a conflict occur ()
Binlog checksum verification at recovery time ()
Verbose print-out of by ()
from validates when binlog checksummed ()
Freeing memory of ()
Corrected verbose output for multi-record Rows-log-event ()
no longer causes crash ()
that were running an index condition pushdown in InnoDB/XtraDB will now return an error ()
As per the , this will be the last release of for CentOS/RHEL 6.x
As per the , this will be the final release of
Fixes for the following :
()
For a complete list of changes made in with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 15 Dec 2016
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 5.6.34-79.1
updated to 5.6.34-79.1
updated to 9.4
The limit for the system variable has been increased to 1024K
updated to 25.3.19
packages for Debian 9 "stretch" amd64 and Debian 8 "jessie" ppc64el added
Fixes for the following :
CVE-`-```
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 30 Sep 2016
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 5.6.32-78.1
updated to 5.6.32-78.1
updated to 5.6.33
updated to 5.6.33
Optimizer sometimes use "index" instead of "range" access for UPDATE ()
Fixes for the following :
This vulnerability was discovered by .
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 28 Jan 2020
MariaDB 10.1 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.44 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 5.6.47
updated to 5.6.46-86.2
updated to 5.6.46-86.2
MDEV-21337: fix aligned_malloc()
MDEV-21343: Threadpool/Unix- wait_begin() function does not wake/create threa ds, when it should
Bug#29630767: Use of uninitialized value in libmysql (client.cc function run_plugin_auth)
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
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.44, with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.44, see the MariaDB Foundation release announcement.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 8 May 2019
MariaDB 10.1 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.40 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
This release fixes a regression that was introduced by MariaDB 10.1.39 — by the first installation (not upgrades) of MariaDB rpm packages on a non-systemd Linux distribution, such as CentOS6, the newly created /var/lib/mysql was created with too restrictive file permissions, so clients could not access the unix socket /var/lib/mysql/mysql.sock.
Apart from the above bug fix, this release is identical to MariaDB 10.1.39.
Fixes for the following :
CVE-`-```
For a complete list of changes made in MariaDB 10.1.40, with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.40, see the MariaDB Foundation release announcement.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 10 Aug 2017
MariaDB 10.1 is the previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.26 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
The default for is now ON (see MDEV-13247)
updated to 8.41
updated to 5.6.36-82.1
updated to 5.6.36-82.1
updated to 5.6.37
updated to 5.6.37
MariaDB Backup is now stable (GA)
New options
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Ubuntu 16.10 "Yakkety" and Fedora 24
Fixes for the following :
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
For a complete list of changes made in MariaDB 10.1.26, with links to detailed information on each push, see the changelog.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 4 Jul 2017
MariaDB 10.1 is the previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.25 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
MariaDB can no longer be compiled with OpenSSL version 0.9.8 and below. The last 0.9.8 release was in December 2015, it is out of support and is no longer getting security fixes.
MariaDB Backup is now beta
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Ubuntu 16.10 "Yakkety"
Fixes for the following :
CVE-`-```
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
Updating from MariaDB 10.1.21 to MariaDB 10.1.22 or higher is highly recommended due to two high-priority regression fixes. See MDEV-11842 and MDEV-12075 for details.
For a complete list of changes made in MariaDB 10.1.25, with links to detailed information on each push, see the changelog.
DownloadRelease NotesChangelogOverview of 10.1
Release date: 3 May 2017
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.23 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
Updating from MariaDB 10.1.21 to MariaDB 10.1.22 or higher is highly recommended due to two high-priority regression fixes. See MDEV-11842 and MDEV-12075 for details.
MDEV-12602: Fixed some race conditions in InnoDB encryption
MariaDB Backup alpha introduced, see this blog post for more information
Galera wsrep library updated to 25.3.20
Packages for Ubuntu 17.04 "zesty" added
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Ubuntu 12.04 LTS "Precise" and Mint 13 LTS "Maya"
Fixes for the following :
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
For a complete list of changes made in MariaDB 10.1.23, with links to detailed information on each push, see the changelog.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 30 Aug 2016
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.17 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 5.6.31-77.0
updated to 5.6.31-77.0
updated to 5.6.32
updated to 5.6.32
The CONNECT engine now supports the - MDEV-9765.
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Fedora 22
Packages for Fedora 24 are now available
Fixes for the following :
CVE-2016-6662 (MDEV-10465). That allowed a malicious user to create a my.cnf in the datadir and, under certain circumstances, execute arbitrary code as mysql (or even root) user. This vulnerability was discovered by Dawid Golunski.
Galera wsrep library updated to 25.3.17
The support for system variable has now been added and thus its values will no longer be ignored by the server. In order to be backward compatible its default value has been changed to 0 (from 131072), which essentially allows writesets of any size.
The default value of has been raised from 1GB to 2GB.
For a complete list of changes made in MariaDB 10.1.17, with links to detailed information on each push, see the changelog.
MariaDB-10.1.15 was never released, MariaDB 10.1.16 is the release that followed MariaDB 10.1.14.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 1 Jul 2016
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.15 was not released.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 5.6.30-76.3
updated to 5.6.31
updated to 5.6.31
updated to 8.39
updated to 5.6.30-76.3
updated to 9.3
Added the utf8_thai_520_w2, utf8mb4_thai_520_w2, ucs2_thai_520_w2, utf16_thai_520_w2 and utf32_thai_520_w2 .
Various packages and bintar builds for POWER8 ppc64 and ppc64le architectures now available
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Ubuntu 15.10 "wily"
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.15, with links to detailed information on each push, see the changelog.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 29 Jan 2016
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.11 is a Stable (GA) release.
For a complete overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
New authentication plugin for clients connecting on Windows using .
New .
Galera library has been updated from 25.3.9 to 25.3.12.
Fixes for the following :
CVE-`-```
This release includes all bug fixes from MariaDB 5.5.47, MariaDB 10.0.23, andMariaDB Galera Cluster 10.0.23 releases.
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Ubuntu 15.04 "Vivid".
For a complete list of changes made in MariaDB 10.1.11, with links to detailed information on each push, see the changelog.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 18 Jul 2016
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.16 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 5.6.30-76.3
updated to 5.6.31
updated to 5.6.31
updated to 8.39
updated to 5.6.30-76.3
updated to 9.3
Various packages and bintar builds for POWER8 ppc64 and ppc64le architectures now available
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Ubuntu 15.10 "wily"
For a complete list of changes made in MariaDB 10.1.16, with links to detailed information on each push, see the changelog.
The most recent release of is: Stable (GA)
Release date: 8 Nov 2019
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
: InnoDB fails to start when FTS table has FK relation
See also the release notes for for additional items of note
Fixes for the following :
CVE-`-```
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 2 May 2019
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
Starting with this release, we are now providing for
updated to 5.6.44
updated to 8.43
updated to 5.6.43-84.3
updated to 5.6.43-84.3
- Add option to PAM authentication plugin to allow case insensitive username matching
- InnoDB fails to rollback after exceeding FOREIGN KEY recursion depth
- Data corruption will happen on the Galera cluster size change
- Merge InnoDB and XtraDB changes from MySQL 5.6.44
As per the , this will be the last release of for Ubuntu 14.04 Trusty
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 6 Feb 2019
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 9.5
: Maximum value of is now 2097152
: InnoDB should use case-insensitive column name comparisons like the rest of the server
ALTER TABLE fixes: , , , ,, ,
Improvements to InnoDB page checksum, recovery, and mariadb-backup: ,, , ,
Galera
: Galera durability fix
New configuration variable wsrep_certification_rules, used for
controlling whether to use new/optimized
(--wsrep_certification_rules=optimized) certification rules or the
old/classic ones (--wsrep_certification_rules=strict). Setting the
variable to strict can cause more certification failures.
Debian has stopped supporting the ppc64el architecture for Debian 8 Jessie and so this is the last release of on Jessie for that architecture
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 2 Nov 2018
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
Various fixes from MySQL 5.6.42: , ,
: fixed a bug with DDL and FOREIGN KEY
Fulltext index fixes:
: extended the range of on 64-bit systems
: InnoDB fts_query() ignores KILL
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 8 Sep 2018
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 5.6.41-84.1
updated to 5.6.41-84.1
if available, stunnel can be used during -
fix of regression introduced in 10.1.32:
fix of regression affecting 10.1.35 only: InnoDB fails to drop large temporary table on disconnect
Galera: wsrep_sst_rsync does not support innodb_data_home_dir
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 7 Aug 2018
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
New variable, for specifying whether to write a core file on crash.
ALTER TABLE:
Bug #25928471: ONLINE ALTER AND CONCURRENT DELETE ON TABLE WITH MANY TEXT COLUMNS CAUSES CRASH
XA: Assertion `!clust_index->online_log' failed in rollback_inplace_alter_table
InnoDB lock->index refers to a freed object after failed ADD INDEX
fil_rename_tablespace() times out and crashes server during table-rebuilding ALTER TABLE
Alter InnoDB Partitioned Table Moves Files (which were originally not in the datadir) to the datadir
On schema mismatch in IMPORT TABLESPACE, display ROW_FORMAT in clear text
Fulltext search:
Bug #27041445 SERVER ABORTS IF FTS_DOC_ID EXCEEDS FTS_DOC_ID_MAX_STEP
Bug #26334149 - MYSQL CRASHES WHEN FULL TEXT INDEXES IBD FILES ARE ORPHANED DUE TO RENAME TABLE
Bug #27326796 - MYSQL CRASH WITH INNODB ASSERTION FAILURE IN FILE PARS0PARS.CC
Fix fts_sync_synchronization in InnoDB
Wrong INFORMATION_SCHEMA.INNODB_BUFFER_PAGE.TABLE_NAME
InnoDB error "returned OS error 71" complains about wrong path
: Windows - redo log does not work on native 4K sector disks
(also fixes some adaptive hash index corruption that can cause data corruption)
Galera : WSREP: BF lock wait long for trx
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 22 Dec 2017
is the previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
- Rollback progress log messages during crash recovery are intermixed with unrelated log messages
- install_db shows corruption
- innodb.drop_table_background failed
- Assertion failing: `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())
- Rollback progress log messages during crash recovery are intermixed with unrelated log messages
- InnoDB shutdown should not be blocked by a large transaction rollback
- InnoDB may hang if shutdown is initiated soon after startup while rolling back recovered incomplete transactions
- WSREP: BF lock wait long
- dict_stats_process_entry_from_defrag_pool() fails to call dict_table_close() when index==NULL
As per the , this will be the last release of for Ubuntu 17.04 "zesty"
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 14 Nov 2017
is the previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
will be a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
mariadb-backup --apply-log-only crashes if incomplete transactions with update_undo logs are present
Fix backup for Innodb tables with DATA DIRECTORY
mariadb-backup --copy-back: Copy all undo tablespace files
Restore --remove-original option for mariadb-backup
mariadb-backup --incremental --prepare incorrectly sets file size
ALTER TABLE…DISCARD TABLESPACE takes a lot of time
Allow online table rebuild when encryption or compression parameters change
'Undo log record is too big.' error occurring in very narrow range of string lengths
InnoDB: Failing assertion when accessing upon upgrade from 10.1.0 to 10.1.20
MySQL#78423 InnoDB FTS duplicate key error
MySQL#86607 InnoDB crash after failed ADD INDEX and table_definition_cache eviction
: Wrong result after altering a partitioned table
updated to 7.07.
Fixes for the following :
,
For a complete list of changes made in , with links to detailed information on each push, see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
A regression was discovered after the release of . It has been pulled from the downloads system, but some mirrors may still have it. Do not download or install this version. Stay with until 10.1.28 is released.
Release date: 25 Sep 2017
is the previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 5.6.37-82.2
updated to 5.6.37-82.2
Temporary files created by merge sort and row log are encrypted if is set to 1, regardless of whether the table encrypted or not ().
Fixes for the following :
CVE-`-```
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 18 Jan 2017
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 5.6.35
A file format compatibility bug that was introduced in was fixed in this version of MariaDB. Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
updated to 5.6.35
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 10 May 2016
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to XtraDB-5.6.29-76.2
updated to InnoDB-5.6.30
updated to 5.6.30
New variable for setting a directory for storing temporary non-tablespace InnoDB files, .
Fixes for the following :
Our repositories for Debian "Sid" and the newly-released Ubuntu 16.04 "Xenial" use a new GPG signing key. As detailed in , APT 1.2.7 (and later) prefers SHA2 GPG keys and now prints warnings when a repository is signed using a SHA1 key like our existing GPG key. We have created a new SHA2 key for use with these affected repositories.
Information about this key:
The Key ID is: C74CD1D8
The full fingerprint of the new key is: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8
The key can be added using the following command:
The instructions in the for Ubuntu 16.04 "Xenial" and Debian "Sid" have been updated to reference this new key. Repositories for previous versions of Debian and Ubuntu still use the old key, so no changes are needed there.
The Windows compiler used by MariaDB from this release drops Windows XP and Windows Server 2003 support.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 25 Mar 2016
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
(currently distributed in source form only).
new server variables; and .
and are now allowed in .
has a new column; key_id.
The has been updated to version 25.3.15.
The has been updated for a number of plugins.
Fixes for the following :
CVE-`-```
A repository for the newly-released Ubuntu 16.04 "xenial" has been added. Currently the repository is using packages built on Ubuntu 15.10 "wily", but in the next release they will be built on xenial builders.
- APT 1.2.7 (and later) prefers SHA2 GPG keys and now prints warnings when a repository is signed using a SHA1 key. We have created a new SHA2 key for use with our Ubuntu 16.04 "xenial" repository.
The Key ID is: C74CD1D8
The full fingerprint of the new key is: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8
The key can be added using the following command:
The instructions in the for Ubuntu 16.04 "xenial" have been updated to refer to this new key. Repositories for previous versions of Ubuntu will continue to use the old key.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 25 Feb 2016
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For a complete overview of see the page.
Thanks, and enjoy MariaDB!
updated to XtraDB-5.6.28-76.1
updated to InnoDB-5.6.29
updated to 5.6.29
Fixes for the following :
This release includes all bug fixes from , , and releases.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 23 Nov 2015
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For a complete overview of see the page.
Thanks, and enjoy MariaDB!
engine updated to version 1.04.0003.
numerous new .
The field, seconds_behind_master, is now, with , only updated after transactions commit.
Includes all bug fixes from , , and releases.
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 27 Jul 2015
is the current development series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
is extended with TO # clause which allows one to specify the number of the first binary log. ()
New system variables , and .
New system variable for determining how often the buffer pool dump status should be printed in the logs.
was enabled and updated to 5.04 (earlier versions of Mroonga did not work in 10.1).
Added support for for compatibility with MySQL.
New status variables and for tracking the number of CREATE/DROP TEMPORARY TABLE statements.
Fixes for the following :
CVE-`-```
For a complete list of changes made in , with links to detailed information on each push, see the .
sudo apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 0xF1656F24C74CD1D8sudo apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 0xF1656F24C74CD1D8The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 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.1
Alternate download from mariadb.org
Release date: 5 Nov 2019
MariaDB 10.1 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.42 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
MDEV-17638: Improved innochecksum error messages
MDEV-20247: Replication hangs with "preparing" and never starts
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
MDEV-19376: Repl_semi_sync_master::commit_trx assertion
Galera wsrep library updated to 25.3.28
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.42, with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.42, see the MariaDB Foundation release announcement.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 31 Jul 2019
MariaDB 10.1 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.41 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
MDEV-19922: updated to 10.2
MDEV-18328: is now stable and requires the .
Update InnoDB/XtraDB from MySQL 5.6.45 and Percona Server 5.6.44-86.0
ALTER TABLE: MDEV-16060
FULLTEXT INDEX: MDEV-14154, MDEV-18220, MDEV-19441, MDEV-19445
Encryption: MDEV-13983, MDEV-16866
Galera + FOREIGN KEY: MDEV-19660
Recovery & mariadb-backup: MDEV-19978
Other: MDEV-19614, MDEV-20102
MDEV-20091: DROP TEMPORARY table is logged despite no CREATE was logged
MDEV-19491: update query stopped working after mariadb upgrade
MDEV-20110: don't try to load client plugins with invalid names
MDEV-19427: mysql_upgrade_service throws exception upgrading from 10.0 to 10.3
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for OpenSUSE 42.3 and Ubuntu 18.10 "Cosmic"
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.41, with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.41, see the MariaDB Foundation release announcement.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 18 Jun 2018
MariaDB 10.1 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.34 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
MDEV-14589 InnoDB should not lock a delete-marked record
MDEV-16283 ALTER TABLE...DISCARD TABLESPACE still takes long on a large buffer pool
MDEV-15824 innodb_defragment=ON trumps innodb_optimize_fulltext_only=ON in OPTIMIZE TABLE
MDEV-16124 fil_rename_tablespace() times out and crashes server during table-rebuilding ALTER TABLE
MDEV-16416 Crash on IMPORT TABLESPACE of a ROW_FORMAT=COMPRESSED table
MDEV-16456 InnoDB error "returned OS error 71" complains about wrong path
MDEV-13103 Deal with page_compressed page corruption
MDEV-15611 Due to the failure of foreign key detection, Galera slave node killed himself.
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Ubuntu 17.10 Artful
Fixes for the following :
CVE-`-```
For a complete list of changes made in MariaDB 10.1.34, with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.34, see the MariaDB Foundation release announcement.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 6 Feb 2018
MariaDB 10.1 is the previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.31 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 5.6.38-83.0
updated to 5.6.38-83.0
updated to 5.6.39
MDEV-13499 - Backing up table that "doesn't exist in engine" cause crash in mariadb-backup when using encryption
MDEV-7049 MySQL#74585 - InnoDB: Failing assertion: *mbmaxlen < 5 in file ha_innodb.cc line 1904
(XtraDB) MDEV-14174 - crash on start with innodb-track-changed-pages
MDEV-14776 - InnoDB Monitor output generated by specific error is flooding error logs
MDEV-13205 - InnoDB: Failing assertion: !dict_index_is_online_ddl(index) upon ALTER TABLE
MDEV-14874 - innodb_encrypt_log corrupts the log when the LSN crosses 32-bit boundary
MDEV-14799 - After UPDATE of indexed columns, old values will not be purged from secondary indexes
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Fedora 25
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.31, with links to detailed information on each push, see the changelog.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 27 Mar 2018
MariaDB 10.1 is the previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.32 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
MDEV-14533 - Added the , for monitoring disk space
Galera wsrep library updated to 25.3.23
MDEV-14611 - does not work properly when used with DATA DIRECTORY.
MDEV-15333 - MariaDB (still) slow start
MDEV-14904 - Backport
MDEV-12255 - Wrong result with
MDEV-12396 - cleanup
MDEV-14648 - Restore fix for MySQL BUG#39053 - does not allow the storage engine to cleanup open connections
MDEV-15249 - IMPORT fixes
MDEV-14988 - tries to modify files if transactions were recovered in COMMITTED state
MDEV-14773 - hangs for InnoDB table with (fixing a recent regression from upstream)
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.32, with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.32, see the MariaDB Foundation release announcement.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 28 Sep 2017
MariaDB 10.1 is the previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.28 will be a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 5.6.37-82.2
updated to 5.6.37-82.2
MDEV-13787: Crash in persistent stats wsrep_on (thd=0x0)
MDEV-13899: IMPORT TABLESPACE may corrupt ROW_FORMAT=REDUNDANT tables
MDEV-13488: InnoDB writes CRYPT_INFO even though encryption is not enabled (fixes upgrades from 5.5 to 10.1)
MDEV-13437: InnoDB fails to return error for XA COMMIT or XA ROLLBACK in read-only mode
MDEV-13637: InnoDB change buffer housekeeping can cause redo log overrun and possibly deadlocks
MDEV-12988: mariadb-backup fails if innodb_undo_tablespaces>0
MDEV-13471: Test failure on innodb.log_file_size,4k (fixes Galera when using innodb_page_size=4k)
MDEV-13814: Extra logging when innodb_log_archive=ON (XtraDB only)
MDEV-13807: mariadb-backup --apply-log-only does generate redo log by performing rollback and possibly other tasks
MDEV-13684: InnoDB race condition between fil_crypt_thread and btr_scrub_init
Temporary files created by merge sort and row log are encrypted if is set to 1, regardless of whether the table encrypted or not (MDEV-12634).
Fixes for the following :
CVE-`-```
For a complete list of changes made in MariaDB 10.1.28, with links to detailed information on each push, see the changelog.
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 31 May 2017
MariaDB 10.1 is the previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.24 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
Updating from MariaDB 10.1.21 to MariaDB 10.1.22 or higher is highly recommended due to two high-priority regression fixes. See MDEV-11842 and MDEV-12075 for details.
updated to 5.6.36-82.0
updated to 5.6.36-82.0
updated to 5.6.36
updated to 5.6.36
MDEV-12674: Innodb_row_lock_current_waits has overflow
MDEV-12188: information schema - errors populating fail to free memory, unlock mutexes
MDEV-12832: support for streaming in tar format in MariaDB Backup has been removed
MDEV-6262: Fixes from coverity report on MariaDB
default changed from backoff to legacy to prevent potential deadlock issue in I/O-bound workloads with several small buffer pool instances in combination with small redo log files (see #1651657.)
Fixes for the following :
CVE-`-```
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
For a complete list of changes made in MariaDB 10.1.24, with links to detailed information on each push, see the changelog.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 14 Mar 2017
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.22 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
Updating from MariaDB 10.1.21 to MariaDB 10.1.22 is highly recommended due to two high-priority regression fixes. See below for links to the relevant MDEVs.
updated to 5.6.35-80.0
updated to 5.6.35-80.0
updated to 8.40
MDEV-11842: Fix a 10.1.21 regression with failed INSERT, BEFORE INSERT triggers, and columns with no default value
MDEV-12075: Fix a 10.1.21 regression in the InnoDB data file extension code
MDEV-11027: better InnoDB crash recovery progress reporting
MDEV-11520: improvements to how InnoDB data files are extended
Improvements to InnoDB startup/shutdown to make it more robust
MDEV-11233: fix for FULLTEXT index crash
MDEV-9734: compatible bintar files now available
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Fedora 23, CentOS 5, RHEL 5, and openSUSE 13
OpenSUSE 42 repositories have been added in this release
Fixes for the following :
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
For a complete list of changes made in MariaDB 10.1.22, with links to detailed information on each push, see the changelog.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 17 Oct 2015
MariaDB 10.1 is the current stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.8 is a Stable (GA) release.
The release notes here only document changes from the previous version ofMariaDB 10.1. For a complete overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to XtraDB-5.6.26-74.0
systemd support has been added for those distributions that support it.
For tables, the option enables IETF-compatible parsing of embedded quote and comma characters (MDEV-8682).
now supports IPv6 (MDEV-8034).
--silent-startup . If specified, mysqld does not
print Notes to log during startup.
Replication from MySQL 5.6 with GTID, binlog_rows_query_log_events and ignorable events now works. In this case MariaDB will remove the MySQL GTIDs and other unneeded events and instead adds its own.
New proxy server option for the , , for use when http calls cannot be made, such as in a firewall environment.
Explicit or implicit casts from MAX(string) to INT, DOUBLE or DECIMAL now produce warnings (MDEV-8852).
For a complete list of changes made in MariaDB 10.1.8, with links to detailed information on each push, see the changelog.
The most recent release of is: Stable (GA)
Release date: 9 May 2018
is the previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
updated to 8.42
The embedded server library now supports SSL when connecting to remote servers.
ALTER TABLE fixes: , ,
encryption fixes: , , ,
systemd and shutdown fixes:
As per the , this will be the last release of for Debian 7 Wheezy
In this release experimental Ubuntu 18.04 "bionic" packages are present in the repository. However, because Ubuntu includes in its main repositories we recommend using the Ubuntu provided packages for general use.
Fixes for the following :
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 24 Dec 2015
is the current stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For a complete overview of see the page.
Thanks, and enjoy MariaDB!
updated to 3.2.37
new variable,
: now supports --persistent option, when used
together with --analyze option, it will force for
this table to be updated.
: On POWER8 architecture MariaDB now uses hardware accelerated crc32.
New variable specifies the percentage of the to dump.
Fixes for the following :
: : Fixed incorrect implementation of the --ssl-verify-server-cert
option that allowed a malicious attacker (with a capability to perform a
man-in-the-middle attack) to replace the server SSL certificate, bypassing
the client-side hostname verification. This vulnerability was discovered by
Paul Kehrer and Alex Gaynor.
This release includes all bug fixes from , , and releases.
Previous builds of for Suse Linux Enterprise Server (SLES) 11 only supported SLES 11 SP3 and SP4. Starting with this release, SLES 11 builds for x86_64 also support SLES 11 SP1 and SP2.
As per the , this will be the last release of for Fedora 21.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 13 Apr 2015
is the current development series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
Lots of changes related to encryption. See the . In particular:
The distinction between “tablespace encryption” and “page encryption” was removed, now there is only one single encryption feature. One can use both per-table encryption options and the global option at the same time.
Per table PAGE_ENCRYPTION option that could accept values of ON and OFF was renamed to ENCRYPTED with values YES and NO.
Per table PAGE_ENCRYPTION_KEY was renamed to ENCRYPTION_KEY_ID.
Global variable innodb_default_page_encryption_key become a session .
The command-line option can take the value of FORCE. In this case XtraDB/InnoDB will refuse to create unencrypted tables (CREATE TABLE ... ENCRYPTED=NO will fail).
XtraDB/InnoDB on disk format for encrypted tablespaces and logs was changed. Tables encrypted in 10.1.3 may fail to open.
Key management plugins were renamed not to have “plugin” in the name, for example, “file_key_management_plugin” is now “file_key_management”.
“Key management plugin” type was expanded and renamed to match the new broader set of responsibilities. It is now called .
Command-line option innodb-scrub-log-interval was renamed to and now sets the log scrubbing speed in bytes per second.
Command-line option innodb-scrub-force-testing was renamed to innodb-debug-force-scrubbing.
Consistent support for IF EXISTS, IF NOT EXISTS, and OR REPLACE clauses was added to:
and ()
and ()
and ()
New status variables to show the number of grants on different objects (see ).
New server variable
xid cache scalability was significantly improved (by using lock-free hash)
definitions are now cached in memory (in the table definition cache).
New status variables to track MASTER_GTID_WAIT time. This feature was contributed by Daniel Black. See .
New status variable . This feature was contributed by Daniel Black.
Starting with this release, commits in certain instances in parallel replication complete immediately, avoiding losing throughput when many transactions need conflicting locks. See .
can now analyze leaf pages to estimate how fragmented an index is and how much benefit can be gained from defragmentation.
Fixes for the following :
CVE-`-```
Repositories exist for 10.1, but because 10.1 is still Beta, they are not visible in the . To configure a 10.1 apt, yum, or zypper repository using the tool, simply select 10.0 and then when executing the instructions, manually change all occurrences of '10.0' to '10.1'.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of is: Stable (GA)
Release date: 4 Jun 2015
is the current development series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
New status variables , , and used to examine which triggers caused a group commit to be made.
has been speeded up for large tables ()
A new column, INFO_BINARY, has been added to the in order to avoid truncating queries with binary data ()
updated to 3.2.21.
updated to 1.03.0007
Encryption for temporary files: temporary files created by the server (for binary log caches, for filesort, etc) are now encrypted if the encryption plugin is loaded and --encrypt-tmp-files was specified.
Numerous bugfixes.
New system variable allowing statement digests to be calculated using different lengths.
upgraded to 1.3.0, including the QUERY_DCL filter option.
As per the , this will be the final release of for Fedora 19 "Schrödinger's Cat", Ubuntu 10.04 LTS "Lucid", and Mint 9 LTS "Isadora". When the next version of is released, repositories for these distributions will go away.
We have also added a couple of new Linux distributions with this release. Both Fedora 21 and Ubuntu 15.04 "Vivid" repositories are now available. As this is the first release with these repositories, they are considered experimental. Please if you run into any issues with them.
Repositories exist for 10.1, but because 10.1 is still Beta, they are not visible in the. To configure a 10.1 apt, yum, or zypper repository using the tool, simply select 10.0 and then when executing the instructions, change all occurrences of '10.0' to '10.1'.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 17 October 2014
MariaDB 10.1 is the current development series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.1 is an Alpha release.
Do not use alpha releases on production systems!
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
This is the second alpha release in the MariaDB 10.1 series.
Notable changes of this release include:
for row-based events.
allow roles to be enabled automatically when a user connects.
InnoDB: merged the Facebook/Kakao defragmentation patch (see ) which uses to defragment InnoDB tablespaces).
tables no longer use .frm files.
Galera is merged into MariaDB server, MariaDB 10.1.1 binaries automatically support Galera out of the box.
InnoDB: report progress of inplace alter table (Kakao patch).
can now be aborted.
statement now supports .
.
The has been deprecated. Engine condition pushdown is now always enabled for all engines that support it.
New Information Schema table shows for every system variable its session and global variable values as well as various metadata.
Information Schema plugins can now support SHOW and FLUSH statements. New statements in this release:
Two new columns added to the and Information Schema tables (TOTAL_SSL_CONNECTIONS and MAX_STATEMENT_TIME_EXCEEDED).
MariaDB can execute without a temporary table. (MySQL 5.7 patch)
@@sql_log_slow is now a session variable, not global.
Merge with MariaDB 10.0.14
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for both Ubuntu 13.10 "Saucy" and Mint 16 "Petra".
With the recent release of CentOS 7 and RHEL 7, we are pleased to now provide packages for both distributions. Instructions for how to enable the repositories can be found by visiting the "" page and the repository configuration tool.
Do not use alpha releases on production systems!
For a complete list of changes made in MariaDB 10.1.1, with links to detailed information on each push, see the changelog.
The most recent release of is: Stable (GA)
Release date: 10 Aug 2020
is a previous stable series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
Limit to 255 ().
Minimum value of raised to 8 (previously 4) so fixed size like and are not truncated for lower values of max_sort_length ().
updated to 5.6.49
Fixed corruption in delete buffering ()
Fixed a deadlock in FLUSH TABLES…FOR EXPORT ()
InnoDB data file extension is not crash-safe ()
Minor fixes related to encryption and FULLTEXT INDEX
Crash recovery fix ()
Make the binlog dump thread to log into errorlog a requested GTID position ()
Fix stop of the optimistic parallel slave at requested START-SLAVE-UNTIL position ()
Properly handle RESET MASTER TO value, when the value exceeds the max allowed 2147483647 ()
Correct 'relay-log.info' updating by concurrent parallel workers ()
Eliminate deadlock involving parallel workers, STOP SLAVE and FLUSH TABLES WITH READ LOCK ()
ALTER TABLE ... ANALYZE PARTITION ... with EITS reads and locks all rows ... ()
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 ()
LATERAL DERIVED is not clearly visible in EXPLAIN FORMAT=JSON, make LATERAL DERIVED tables visible in EXPLAIN FORMAT=JSON output ()
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 ()
updated to 5.6.49-89.0
updated to 5.6.49-89.0
MariaDB could crash after changing the query_cache size ()
Errors and SIGSEGV on CREATE TABLE w/ various charsets ()
Crash in CREATE TABLE AS SELECT when the precision of returning type = 0 ()
XA: Reject DDL operations between PREPARE and COMMIT ()
Fixes for the following :
For a complete list of changes made in with links to detailed information on each push, see the .
For a full list of contributors to , see the .
A file format compatibility bug that was introduced in was fixed in . Using or non-default created files that were incompatible with or MySQL 5.6. and higher will convert affected files from earlier releases to a compatible format.This prevents a downgrade to earlier versions.
The most recent release of is: Stable (GA)
Release date: 2 Mar 2015
is the current development series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is a release. One should not expect any notable new features or incompatible interface changes in 10.1 after this release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
This is the first beta release in the series. One should not expect any notable new features or incompatible interface changes in 10.1 after this release.
.
() and two new associated system variables:
Enhanced semisync replication ()
Consistent support for IF EXISTS, IF NOT EXISTS, and OR REPLACE clauses:
These statements now also support IF NOT EXISTS and OR REPLACE:
()
()
()
()
()
()
These statements now support IF EXISTS:
()
()
Dump Thread Enhancements from Google ()
The system variable for permitting dirty reads.
new read-only server variable that shows the version of currently used SSL library.
new command-line option that makes it possible to disable historical "unambiguous prefix" matching in the command-line option parsing.
table has a new IS_DEFAULT column (). See .
table has a new ALGORITHM column ().
Improved concurrency: table definition cache now has lock-free implementation completely avoiding any global locks.
now supports and prints more optimizations (range+MRR, "range checked for each record", full scan on NULL key, expensive constants, etc)
Do not use beta releases on production systems!
Repositories exist for 10.1, but because 10.1 is still Beta, they are not visible in the . To configure a 10.1 apt, yum, or zypper repository using the tool, simply select 10.0 and then when executing the instructions, manually change all occurrences of '10.0' to '10.1'.
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 7 Dec 2014
MariaDB 10.1 is the current development series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
This is an Alpha release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
This is the third alpha release in the MariaDB 10.1 series.
Notable changes of this release include:
option to use the MySQL-5.6 low level formats to store , and types. (MDEV-5528)
Support for Spatial Reference systems for the GIS data (MDEV-60), new REF_SYSTEM_ID column attribute can be used to specify Spatial Reference System ID for columns of spatial data types:
CREATE TABLE t1(g GEOMETRY(9,4) REF_SYSTEM_ID=101);It can be queried via the table.
table.
Per-query variables - see (MDEV-5231)
Scalability fixes (MDEV-7004). Up to 60% higher throughput in sysbench benchmarks on Power8.
password validation plugin. It can enforce a minimum password length and guarantee that a password contains at least a specified number of uppercase and lowercase letters, digits, and punctuation characters.
Assisted discovery in the OQGRAPH Storage Engine (MDEV-5871)
password validation plugin. It only allows passwords that are strong enough to pass CrackLib test. This is the same test that pam_cracklib.so does, installed by default on many Linux distributions.
The number of rows affected by a slow UPDATE or DELETE is now recorded in the - see also . (MDEV-4412)
now supports microseconds in the timeout, no longer rounding fractions to the nearest integer (MDEV-4018)
domain_id based replication filters - see (MDEV-6593)
Two new Information Schema tables for examining wsrep information, and (MDEV-7053)
innodb_log_compressed_pages is now set to OFF by default.
The Facebook Prefix Index Queries Optimization (MDEV-6929), enabled with innodb_prefix_index_cluster_optimization and two new status variables, and to track its effectiveness.
Default size of changed from 8192 to 16384 and from 8192 to 24576 to avoid the need for simple queries with one join to call my_malloc.
Other Webscale patches (MDEV-6039)
were removed, as it was decided to rather implement the feature in a standard way.
Do not use alpha releases on production systems!
Repositories exist for 10.1, but because 10.1 is still Alpha, they are not visible in the repository configuration tool. To configure a 10.1 apt, yum, or zypper repository using the tool, simply select 10.0 and then when executing the instructions, manually change all occurrences of '10.0' to '10.1'.
For a complete list of changes made in MariaDB 10.1.2, with links to detailed information on each push, see the changelog.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 12 May 2020
MariaDB 10.1 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.45 is a Stable (GA) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to 11.0 (MDEV-22032)
InnoDB ALTER TABLE fixes (MDEV-21564, MDEV-19092, MDEV-21549)
InnoDB FULLTEXT INDEX fixes (MDEV-21563)
Corruption for SET GLOBAL innodb_ string variables (MDEV-22393)
wsrep performance optimization (MDEV-7962)
Test suite, Add JUnit support to MTR to generate XML test result (MDEV-22176)
parameter, --ignore-table-data, added (MDEV-22037)
Refactored MYSQL_BIN_LOG::xid_count_per_binlog to satisfy UBSAN enabled build (MDEV-20923)
Unregister of slave threads disconnected before COM_BINLOG_DUMP (Bug#29915479)
Server can fail while replicating conditional comments (Bug#28388217)
Galera wsrep library updated to 25.3.29
Added the xml-report option to (MDEV-22176)
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Debian 8 "Jessie"
Fixes for the following :
For a complete list of changes made in MariaDB 10.1.45, with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.1.45, see the MariaDB Foundation release announcement. Thanks, and enjoy MariaDB!
A file format compatibility bug that was introduced in MariaDB 10.1.0 was fixed in MariaDB 10.1.21. Using or non-default created files that were incompatible with MariaDB 10.0 or MySQL 5.6. MariaDB 10.1.21 and higher will convert affected files from earlier MariaDB 10.1 releases to a compatible format.This prevents a downgrade to earlier MariaDB 10.1 versions.See the commit for details.
The most recent release of is: Stable (GA)
Release date: 30 Jun 2014
is the current development series of MariaDB. It is an evolution of with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
is an release.
For an overview of see the page.
Thanks, and enjoy MariaDB!
This is the first alpha release in the series.
Notable changes of this release include:
InnoDB/XtraDB
, Allow > 16K pages on InnoDB - InnoDB now allows to be configured as 16K, 32K and 64K. Note that single row size must be < 16K. This feature will allow especially more blob columns to be created.
, Force PK option - Added a new dynamic configuration variable default off. If option is true, create table without primary key or unique key where all keyparts are NOT NULL is not accepted. Instead an error message is printed. Variable value can be changed with set global innodb_force_primary_key = .
Security
, enhance security using special compilation options - MariaDB is now compiled with security hardening options by default. It is an additional protection layer that makes new, yet unknown, security vulnerabilities more difficult to exploit.
Storage Engine functionality
, merge default_tmp_storage_engine - Added server variable and the command line option.
, Don't create frm files for temporary tables - Temporary tables no longer create frm files on disk. Which means that if the temporary table is created in the engine, it will not touch the disk at all.
The storage engine is no longer enabled by default, and the plugin needs to be specifically enabled.
The storage engine is no longer enabled by default, and the plugin needs to be specifically enabled.
Optimizer
, - Check how close the optimizer's estimates about the query plan are to the reality.
Administration
, GUI-friendly cmake options to enable/disable plugins - MariaDB now uses PLUGIN_xxx cmake options to enable or disable plugins, not a combination of WITH_xxx, WITHOUT_xxx, WITH_PLUGINX_xxx, WITHOUT_PLUGIN_xxx, WITH_xxx_STORAGE_ENGINE, WITHOUT_xxx_STORAGE_ENGINE. See .
Improvements from WebScaleSQL
Fix errors detected by at compile time - Not merged but ASan was run against MariaDB. It generated the following:
- Compile/run MariaDB with ASan (fixed in 10.0.13)
- TokuDB: ERROR: AddressSanitizer: attempting to call malloc_usable_size() for pointer which is not owned: 0x601200008f80 (not fixed)
- ‘explain_node’ may be used uninitialized in this function (not fixed)
- TokuDB: hatoku_hton.cc:1021:5: warning: ‘do_commit’ may be used uninitialized in this function (not fixed)
, Fix errors detected by ASan at runtime. Merged to 5.5.39.
Use single quotes for perl paths, in case of special symbols. Merged to 10.0.13.
Stop spawning dummy threads on client library initialization. Merged to 10.0.13.
Performance
, Disable by default
, Merge 10.0.10-FusionIO to 10.1 - , are available for Fusion-IO devices in 10.1.0
Do not use alpha releases on production systems!
For a complete list of changes made in , with links to detailed information on each push, see the .
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.1
Release date: 9 Sep 2015
MariaDB 10.1 is the current development series of MariaDB. It is an evolution of MariaDB 10.0 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.1.7 is a Release Candidate (RC) release.
For an overview of MariaDB 10.1 see theWhat is MariaDB 10.1? page.
Thanks, and enjoy MariaDB!
updated to XtraDB-5.6.25-73.1
MariaDB can now also encrypt (including relay
logs). To enable binary logs make sure
that an encryption plugin is loaded and add encrypt-binlog to
your my.cnf file.
The variable no longer affects the replication of events in a Galera cluster.
SQL standards-compliant behavior when dealing with .
Default values of server variables were changed as follows:
Variable name
Old value
New value
128K
256K
1M
4M
0
1M
ON
OFF
OFF
ON
NO_ENGINE_SUBSTITUTION,NO_AUTO_CREATE_USER
0
10000
0
10000
0
10000
400
2000
One can now explicitly request MariaDB to select a good value for certain
command-line options by using the --autoset prefix. For example,
in my.cnf:
[mysqld]
autoset-back-logAt the moment only the back-log and host-cache-size options support this prefix.
Fixes for the following :
CVE-`-```
For a complete list of changes made in MariaDB 10.1.7, with links to detailed information on each push, see the changelog.
MariaDB 10.1 is no longer maintained. Please use a more recent release.
The most recent release of MariaDB 10.1 is:MariaDB 10.1.48 Stable (GA) Download Now
MariaDB 10.1 is a previous stable version of MariaDB. The first stable release was in October 2014.
For details on upgrading from MariaDB 10.0, see .
The following lists the major new features in MariaDB 10.1:
Galera, a true multi-master solution, is a standard part of MariaDB 10.1.
Two new Information Schema tables for examining wsrep information, and (MDEV-7053)
.
Page compression for .
domain_id based replication filters - see (MDEV-6593)
Enhanced semisync replication; Wait for at least one slave to acknowledge transaction before committing (MDEV-162).
for row-based events.
Dump Thread Enhancements from Google. Makes multiple slave setups faster by allowing concurrent reading of binary log. (MDEV-7257)
Commits in certain instances in parallel replication complete immediately, avoiding losing throughput when many transactions need conflicting locks. See .
is extended with TO # which allows one to specify the number of the first binary log. (MDEV-8469)
Due to the implementation of SQL standards-compliant behavior when dealing with , in certain edge cases, there may be replication issues when replicating from a MariaDB 10.0 master to a MariaDB 10.1 slave using . See MDEV-12248.
(MDEV-5210).
New columns for the table.
by several fixes for real-world cases.
Don't create frm files for temporary tables (MDEV-4260).
can be used to automatically abort long running queries. (MDEV-4427).
works without usage of a temporary table (MDEV-334). The feature was backported from MySQL 5.7
Scalability fixes (MDEV-7004). Up to 60% higher throughput in sysbench benchmarks on Power8.
Make simple queries faster as we call malloc() fewer times.
Automatic discovery of tables (simpler mysql_install_db code). (MDEV-4262), tables no longer use .frm files.
Other Webscale patches (MDEV-6039)
MDEV-7728 xid cache scalability was significantly improved (by using lock-free hash)
Support for Spatial Reference systems for the GIS data (MDEV-60), new REF_SYSTEM_ID column attribute can be used to specify Spatial Reference System ID for columns of spatial data types:
table.
table.
statements. New statements include:
New columns for the and tables.
provides output that looks like EXPLAIN output, but also includes data from the query execution (how many rows were actually read, etc).
is a re-implementation of similar feature in MySQL 5.6
produces detailed information about the statement execution
now supports microseconds in the timeout, no longer rounding fractions to the nearest integer (MDEV-4018)
.
The number of rows affected by a slow UPDATE or DELETE is now recorded in the - see also . (MDEV-4412)
SQL standards-compliant behavior when dealing with . Note that this could cause replication issues in certain edge cases when replicating from a MariaDB 10.0 master to a MariaDB 10.1 slave. using . See MDEV-12248.
Explicit or implicit casts from MAX(string) to INT, DOUBLE or DECIMAL now produce warnings (MDEV-8852).
Allow up to 64K pages in InnoDB (old limit was 16K) (MDEV-6075).
The Facebook/Kakao defragmentation patch (see ) which uses to defragment InnoDB tablespaces).
Added the utf8_thai_520_w2, utf8mb4_thai_520_w2, ucs2_thai_520_w2, utf16_thai_520_w2 and utf32_thai_520_w2 .
For a list of all new variables, see and . Some of these, and other variable-related changes, include:
gives information, like description and value origin, for system variables (MDEV-6138).
MDEV-6858 New server variable
New status variables to show the number of grants on different objects (see )
Default size of changed from 8192 to 16384 and from 8192 to 24576 to avoid the need for simple queries with one join to call my_malloc.
Added variable (From MySQL 5.6) (MDEV-6107).
- set variables for the duration of the query (MDEV-5231). This is a backport of Per-query Variable Statement feature of Percona Server 5.6 (which, in turn, is based in MySQL GSoC 2009 project by Joseph Lukas), with many bugs fixed.
option to use the MySQL-5.6 low level formats to store , and types. (MDEV-5528)
Backport (MDEV-14904)
mysqld --help --verbose now shows valid variables for ENUM variables. (MDEV-6137)
MDEV-6981 New status variables to track MASTER_GTID_WAIT time.
MDEV-7198 New status variable .
--silent-startup . If specified, mysqld does not print Notes to the error log during startup.
(MDEV-6431).
password validation plugin. It can enforce a minimum password length and guarantee that a password contains at least a specified number of uppercase and lowercase letters, digits, and punctuation characters.
password validation plugin. It only allows passwords that are strong enough to pass CrackLib test. This is the same test that pam_cracklib.so does, installed by default on many Linux distributions.
for traditional password-based authentication. A new, secure alternative to the old mysql_native_password plugin.
Enhance security using special compilation options - MariaDB is now compiled with security hardening options by default. It is an additional protection layer that makes new, yet unknown, security vulnerabilities more difficult to exploit. (MDEV-5730)
For a complete list of security vulnerabilities (CVEs) fixed across all versions of MariaDB, see the page.
CVE-2021-2144: MariaDB 10.1.42CVE-2021-2022: MariaDB 10.1.46CVE-2021-2011: MariaDB 10.1.33CVE-2021-2007: MariaDB 10.1.41CVE-2020-2922: MariaDB 10.1.41CVE-2020-28912: MariaDB 10.1.48CVE-2020-2814: MariaDB 10.1.45CVE-2020-2812: MariaDB 10.1.45CVE-2020-2780: MariaDB 10.1.42CVE-2020-2752: MariaDB 10.1.45CVE-2020-2574: MariaDB 10.1.44CVE-2020-15180: MariaDB 10.1.47CVE-2020-14812: MariaDB 10.1.48CVE-2020-14765: MariaDB 10.1.48CVE-2020-14550: MariaDB 10.1.33CVE-2019-2974: MariaDB 10.1.42CVE-2019-2805: MariaDB 10.1.41CVE-2019-2740: MariaDB 10.1.41CVE-2019-2739: MariaDB 10.1.41CVE-2019-2737: MariaDB 10.1.41CVE-2019-2627: MariaDB 10.1.39CVE-2019-2614: MariaDB 10.1.39CVE-2019-2537: MariaDB 10.1.38CVE-2019-2529: MariaDB 10.1.38CVE-2019-2503: MariaDB 10.1.36CVE-2019-2455: MariaDB 10.1.33CVE-2018-3282: MariaDB 10.1.37CVE-2018-3251: MariaDB 10.1.37CVE-2018-3174: MariaDB 10.1.37CVE-2018-3156: MariaDB 10.1.37CVE-2018-3143: MariaDB 10.1.37CVE-2018-3133: MariaDB 10.1.30CVE-2018-3081: MariaDB 10.1.33CVE-2018-3066: MariaDB 10.1.35CVE-2018-3064: MariaDB 10.1.35CVE-2018-3063: MariaDB 10.1.35CVE-2018-3058: MariaDB 10.1.35CVE-2018-2819: MariaDB 10.1.33CVE-2018-2817: MariaDB 10.1.33CVE-2018-2813: MariaDB 10.1.33CVE-2018-2787: MariaDB 10.1.33CVE-2018-2784: MariaDB 10.1.33CVE-2018-2782: MariaDB 10.1.33CVE-2018-2781: MariaDB 10.1.33CVE-2018-2771: MariaDB 10.1.33CVE-2018-2767: MariaDB 10.1.33CVE-2018-2766: MariaDB 10.1.33CVE-2018-2761: MariaDB 10.1.33CVE-2018-2755: MariaDB 10.1.33CVE-2018-2668: MariaDB 10.1.31CVE-2018-2665: MariaDB 10.1.31CVE-2018-2640: MariaDB 10.1.31CVE-2018-2622: MariaDB 10.1.31CVE-2018-2612: MariaDB 10.1.31CVE-2018-2562: MariaDB 10.1.31CVE-2017-3653: MariaDB 10.1.26CVE-2017-3651: MariaDB 10.1.19CVE-2017-3641: MariaDB 10.1.26CVE-2017-3636: MariaDB 10.1.26CVE-2017-3600: MariaDB 10.1.19CVE-2017-3464: MariaDB 10.1.23CVE-2017-3456: MariaDB 10.1.23CVE-2017-3453: MariaDB 10.1.23CVE-2017-3318: MariaDB 10.1.21CVE-2017-3317: MariaDB 10.1.21CVE-2017-3313: MariaDB 10.1.22CVE-2017-3312: MariaDB 10.1.21CVE-2017-3309: MariaDB 10.1.23CVE-2017-3308: MariaDB 10.1.23CVE-2017-3302: MariaDB 10.1.22CVE-2017-3291: MariaDB 10.1.21CVE-2017-3265: MariaDB 10.1.21CVE-2017-3258: MariaDB 10.1.21CVE-2017-3257: MariaDB 10.1.21CVE-2017-3244: MariaDB 10.1.21CVE-2017-3243: MariaDB 10.1.21CVE-2017-3238: MariaDB 10.1.21CVE-2017-15365: MariaDB 10.1.30CVE-2017-10384: MariaDB 10.1.26CVE-2017-10379: MariaDB 10.1.26CVE-2017-10378: MariaDB 10.1.29CVE-2017-10286: MariaDB 10.1.26CVE-2017-10268: MariaDB 10.1.29CVE-2016-9843: MariaDB 10.1.37CVE-2016-8283: MariaDB 10.1.18CVE-2016-7440: MariaDB 10.1.19CVE-2016-6664: MariaDB 10.1.21CVE-2016-6663: MariaDB 10.1.18CVE-2016-6662: MariaDB 10.1.17CVE-2016-5629: MariaDB 10.1.18CVE-2016-5626: MariaDB 10.1.18CVE-2016-5624: MariaDB 10.1.18CVE-2016-5616: MariaDB 10.1.18CVE-2016-5584: MariaDB 10.1.19CVE-2016-5483: MariaDB 10.1.19CVE-2016-5444: MariaDB 10.1.14CVE-2016-5440: MariaDB 10.1.15CVE-2016-3615: MariaDB 10.1.15CVE-2016-3521: MariaDB 10.1.15CVE-2016-3492: MariaDB 10.1.18CVE-2016-3477: MariaDB 10.1.15CVE-2016-3471: MariaDB 10.1.9CVE-2016-3459: MariaDB 10.1.14CVE-2016-3452: MariaDB 10.1.14CVE-2016-2047: MariaDB 10.1.10CVE-2016-0668: MariaDB 10.1.12CVE-2016-0666: [MariaDB 10.1.14]https://mariadb.com/docs/release-notes/mariadb-community-server-release-notes/old-releases/release-notes-mariadb-10-1-series/mariadb-10114-release-notes)CVE-2016-0655: MariaDB 10.1.14CVE-2016-0651: MariaDB 10.1.10CVE-2016-0650: MariaDB 10.1.12CVE-2016-0649: MariaDB 10.1.12CVE-2016-0648: MariaDB 10.1.14CVE-2016-0647: MariaDB 10.1.14CVE-2016-0646: MariaDB 10.1.12CVE-2016-0644: MariaDB 10.1.12CVE-2016-0643: MariaDB 10.1.14CVE-2016-0642: MariaDB 10.1.10CVE-2016-0641: MariaDB 10.1.12CVE-2016-0640: MariaDB 10.1.12CVE-2016-0616: MariaDB 10.1.10CVE-2016-0610: MariaDB 10.1.9CVE-2016-0609: MariaDB 10.1.10CVE-2016-0608: MariaDB 10.1.10CVE-2016-0606: MariaDB 10.1.10CVE-2016-0600: MariaDB 10.1.10CVE-2016-0598: MariaDB 10.1.10CVE-2016-0597: MariaDB 10.1.10CVE-2016-0596: MariaDB 10.1.10CVE-2016-0546: MariaDB 10.1.10CVE-2016-0505: MariaDB 10.1.10CVE-2015-7744: MariaDB 10.1.9CVE-2015-4913: MariaDB 10.1.8CVE-2015-4895: MariaDB 10.1.8CVE-2015-4879: MariaDB 10.1.8CVE-2015-4870: MariaDB 10.1.8CVE-2015-4866: MariaDB 10.1.8CVE-2015-4864: MariaDB 10.1.8CVE-2015-4861: MariaDB 10.1.8CVE-2015-4858: MariaDB 10.1.8CVE-2015-4836: MariaDB 10.1.8CVE-2015-4830: MariaDB 10.1.8CVE-2015-4826: MariaDB 10.1.8CVE-2015-4819: MariaDB 10.1.8CVE-2015-4816: MariaDB 10.1.8CVE-2015-4815: MariaDB 10.1.8CVE-2015-4807: MariaDB 10.1.8CVE-2015-4802: MariaDB 10.1.8CVE-2015-4792: MariaDB 10.1.8
Date
Release
Status
Release Notes
Changelog
3 Nov 2020
Stable (GA)
7 Oct 2020
Stable (GA)
10 Aug 2020
Stable (GA)
12 May 2020
Stable (GA)
28 Jan 2020
Stable (GA)
8 Nov 2019
Stable (GA)
5 Nov 2019
Stable (GA)
31 Jul 2019
Stable (GA)
8 May 2019
Stable (GA)
2 May 2019
Stable (GA)
6 Feb 2019
Stable (GA)
2 Nov 2018
Stable (GA)
8 Sep 2018
Stable (GA)
7 Aug 2018
Stable (GA)
18 Jun 2018
Stable (GA)
9 May 2018
Stable (GA)
27 Mar 2018
Stable (GA)