The most recent release of MariaDB Community Server 10.11 is: 10.11.19 Stable (GA)
Download Community Server 10.11.19
Alternate download from mariadb.org
{% endhint %} Download Release Notes Changelog Overview of 10.11 [*Alternate download from mariadb.org*](https://downloads.mariadb.org/mariadb/10.11.15/) **Release date:** 6 Nov 2025 [MariaDB 10.11](/docs/release-notes/community-server/10.11/what-is-mariadb-1011.md) is a stable long term series of MariaDB, [maintained until](https://mariadb.org/about/#maintenance-policy) February 2028. It is an evolution of [MariaDB 10.10](/docs/release-notes/community-server/old-releases/10.10/what-is-mariadb-1010.md) with several entirely new features. MariaDB 10.11.15 is a ***Stable (GA)*** release. {% hint style="success" %} **For an overview of MariaDB 10.11 see the** [**MariaDB 10.11 Changes & Improvements**](/docs/release-notes/community-server/10.11/what-is-mariadb-1011.md) **page.** {% endhint %} Thanks, and enjoy MariaDB! ## Notable Items ### Storage Engines #### InnoDB * The InnoDB purge subsystem will no longer reset transaction identifiers in freshly inserted records, because it did severely hurt performance in some workloads. ([MDEV-16168](https://jira.mariadb.org/browse/MDEV-16168)) * InnoDB could crash after a DROP TABLE, TRUNCATE TABLE, OPTIMIZE TABLE or a table-rebuilding ALTER TABLE if innodb\_adaptive\_hash\_index entries existed in the table. ([MDEV-26599](https://jira.mariadb.org/browse/MDEV-26599)) * InnoDB could crash if the definition of the InnoDB persistent statistics tables were incorrect. ([MDEV-31740](https://jira.mariadb.org/browse/MDEV-31740)) * Workloads that are bound by innodb\_log\_file\_size would write out unnecessarily many data pages in an attempt to advance the log checkpoint. ([MDEV-35155](https://jira.mariadb.org/browse/MDEV-35155)) * ALTER TABLE could fail to update InnoDB persistent statistics. ([MDEV-35163](https://jira.mariadb.org/browse/MDEV-35163)) * innochecksum misinterprets doublewrite buffer pages ([MDEV-37138](https://jira.mariadb.org/browse/MDEV-37138)) * Crash recovery after bulk load data reports corruption ([MDEV-37192](https://jira.mariadb.org/browse/MDEV-37192)) * InnoDB could crash during the crash recovery of a corrupted database. ([MDEV-37412](https://jira.mariadb.org/browse/MDEV-37412)) * There was a very small chance of InnoDB crashing or misbehaving after an attempt to reduce innodb\_buffer\_pool\_size. ([MDEV-37447](https://jira.mariadb.org/browse/MDEV-37447)) * The forced use of THD accessor functions hurts InnoDB performance ([MDEV-37619](https://jira.mariadb.org/browse/MDEV-37619)) * CHECK TABLE…EXTENDED could flag bogus corruption on a column prefix index. ([MDEV-37659](https://jira.mariadb.org/browse/MDEV-37659)) * During workload after crash recovery, an incorrect (too large) innodb\_buffer\_pool\_pages\_dirty could be reported. ([MDEV-37677](https://jira.mariadb.org/browse/MDEV-37677)) * In rare cases, shutdown might hang ([MDEV-37728](https://jira.mariadb.org/browse/MDEV-37728)) * Lock checks for secondary indexes were unnecessarily accessing some history and could access freed BLOB pages that correspond to column prefixes. ([MDEV-37753](https://jira.mariadb.org/browse/MDEV-37753)) #### Aria * Recovery of Aria transactional tables did not work in big-endian machines like s390x and Sparc ([MDEV-34914](https://jira.mariadb.org/browse/MDEV-34914)) * Failure to detect corruption during backups of Aria table ([MDEV-37520](https://jira.mariadb.org/browse/MDEV-37520)) #### Connect * BsonGet\_String and JsonGet\_String with a NULL argument resulted in an empty string warning. This now has an "Argument is NULL" warning. ([MDEV-37633](https://jira.mariadb.org/browse/MDEV-37633)) #### Federated * FederatedX error 10000 on multi-table UPDATE/DELETE ([MDEV-29874](https://jira.mariadb.org/browse/MDEV-29874)) #### MyISAM * myisamchk -V crashes ([MDEV-37505](https://jira.mariadb.org/browse/MDEV-37505)) #### RocksDB * Corrected python3 compatibility of myrocks\_hotbackup thanks to contributor i18n.site ([MDEV-36010](https://jira.mariadb.org/browse/MDEV-36010)) #### Spider * Server may crash in spider bg mode if multiple queries are sent by spider bg threads consecutively ([MDEV-36325](https://jira.mariadb.org/browse/MDEV-36325)) * Spider: XA COMMIT ONE PHASE fails with "This xid does not exist" ([MDEV-37829](https://jira.mariadb.org/browse/MDEV-37829)) ### Full-text Search * InnoDB could potentially crash if there is any lock conflict on an internal FTS\_%\_CONFIG table of a FULLTEXT INDEX while one of the INFORMATION\_SCHEMA views INNODB\_TRX, INNODB\_LOCKS, or INNODB\_LOCK\_WAITS are being accessed. ([MDEV-36545](https://jira.mariadb.org/browse/MDEV-36545)) * The minimum value of the parameter innodb\_ft\_min\_token\_size was increased to 1, similar to the parameter ft\_min\_word\_len. ([MDEV-37423](https://jira.mariadb.org/browse/MDEV-37423)) ### Sequences * Fixed crashing bug when inserting into a tables with several nextval(sequence) default values. ([MDEV-37172](https://jira.mariadb.org/browse/MDEV-37172)) ### Galera * [Galera](https://mariadb.com/docs/galera-cluster/) updated to 26.4.24 * NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated * Setting wsrep\_slave\_threads causes thread hang when wsrep is not enabled ([MDEV-30418](https://jira.mariadb.org/browse/MDEV-30418)) * MariaDB Cluster server crash during insert when replication filters are used ([MDEV-36134](https://jira.mariadb.org/browse/MDEV-36134)) * Inconsistency detected - create sequence ([MDEV-37366](https://jira.mariadb.org/browse/MDEV-37366)) * InnoDB partition table disallow local GTIDs in galera ([MDEV-37373](https://jira.mariadb.org/browse/MDEV-37373)) * Galera replication does not preserve the character set and collation associated with views, etc. ([MDEV-37857](https://jira.mariadb.org/browse/MDEV-37857)) * MDL conflict between CREATE TRIGGER and INSERT ([MDEV-37965](https://jira.mariadb.org/browse/MDEV-37965)) * Under selinux, the galera SST port checking resulted in excessive AVC notices. This has been simplified under selinux. ([MDEV-37899](https://jira.mariadb.org/browse/MDEV-37899)) ### Plugins * Change several Plugin Maturity Levels ([MDEV-37858](https://jira.mariadb.org/browse/MDEV-37858)) ### Plugin - Audit * Wrong query\_ids are logged by the server\_audit plugin for inserts by triggers when multi-insert statements are used ([MDEV-37434](https://jira.mariadb.org/browse/MDEV-37434)) * Fix server\_audit rwlock Performance Schema instrumentation ([MDEV-37555](https://jira.mariadb.org/browse/MDEV-37555)) ### Plugin - userstat * The number of concurrent connections reported by userstats, when enabled, is updated. ([MDEV-23283](https://jira.mariadb.org/browse/MDEV-23283)) ### Plugin - Hashicorp Key Management * Hashicorp Plugin: enable key version caching by default ([MDEV-30849](https://jira.mariadb.org/browse/MDEV-30849)) ### Optimizer * Prevent MariaDB server crash when a query includes a derived table containing unnamed column. ([MDEV-24588](https://jira.mariadb.org/browse/MDEV-24588)) * Crash when considering Split-Materialized plan ([MDEV-29638](https://jira.mariadb.org/browse/MDEV-29638)) * Wrong result when split optimization is used for grouping with order by and limit ([MDEV-31887](https://jira.mariadb.org/browse/MDEV-31887)) * Correlated derived table query merges can cause crashes, especially with prepared statements. ([MDEV-32294](https://jira.mariadb.org/browse/MDEV-32294)) * Crash if subquery is a UNION of SELECT rand() and uncorrelated SELECT ([MDEV-32403](https://jira.mariadb.org/browse/MDEV-32403)) * UPDATE/DELETE of single table queries would now show r\_table\_time\_ms, and r\_other\_time\_ms during ANALYZE FORMAT=JSON ([MDEV-33309](https://jira.mariadb.org/browse/MDEV-33309)) * Item\_func\_nextval::val\_int() crash on INSERT...SELECT with subqueries ([MDEV-37345](https://jira.mariadb.org/browse/MDEV-37345)) * IS TRUE incorrectly converts outer join to inner ([MDEV-37653](https://jira.mariadb.org/browse/MDEV-37653)) * Wrong result with Loose Scan on QUICK\_GROUP\_MIN\_MAX\_SELECT WITH TIES ([MDEV-37901](https://jira.mariadb.org/browse/MDEV-37901)) * disable\_index\_merge\_plans causes SELECT data loss when more than 100 ORs ([MDEV-37913](https://jira.mariadb.org/browse/MDEV-37913)) ### Optimizer - CTE * Server crash on cleanup of non-fully-constructed-due-to-an-error CTE ([MDEV-32308](https://jira.mariadb.org/browse/MDEV-32308)) ### Parser * very long query cannot be killed quickly ([MDEV-37938](https://jira.mariadb.org/browse/MDEV-37938)) ### Server * LIMIT ROWS EXAMINED prematurely triggers during optimization ([MDEV-22241](https://jira.mariadb.org/browse/MDEV-22241)) * Exchange partition with virtual columns fails ([MDEV-34033](https://jira.mariadb.org/browse/MDEV-34033)) * ALTER TABLE allows adding unique hash key with duplicate values ([MDEV-37296](https://jira.mariadb.org/browse/MDEV-37296)) * LOCATE(X,Y,NULL) is not NULL ([MDEV-37740](https://jira.mariadb.org/browse/MDEV-37740)) ### Locking * DDL in procedure propagates no locking to tables locked by DML ([MDEV-16686](https://jira.mariadb.org/browse/MDEV-16686)) ### Partitioning * Errors or assertion failure upon REPAIR on partitioned Aria table with misplaced rows ([MDEV-33190](https://jira.mariadb.org/browse/MDEV-33190)) ### Platform RedHat * On Fedora, RHEL, and derivatives, depend on the mysql-selinux-1.0.14 package that provides the correct selinux rules for the /usr/sbin/mariadbd that is installed. ([MDEV-24941](https://jira.mariadb.org/browse/MDEV-24941)) ### Stored routines * Crash when calling stored function in FOR loop argument ([MDEV-26115](https://jira.mariadb.org/browse/MDEV-26115)) ### GIS * Several bugs in SPATIAL INDEX page splitting logic could crash InnoDB if the PRIMARY KEY or the SPATIAL data is variable-length. ([MDEV-27675](https://jira.mariadb.org/browse/MDEV-27675)) * Wrong results for self-touching shapes. ([MDEV-31499](https://jira.mariadb.org/browse/MDEV-31499)) ### JSON * Corrected the creation of views on JSON\_TABLEs to require no special privileges. ([MDEV-27898](https://jira.mariadb.org/browse/MDEV-27898)) * View containing JSON\_TABLE does not return JSON ([MDEV-34081](https://jira.mariadb.org/browse/MDEV-34081)) * Wrong result json\_table ([MDEV-36319](https://jira.mariadb.org/browse/MDEV-36319)) * Correct return value of JSON\_VALUE which in the previous release, incorrectly converted a valid empty string return value to a NULL. This has been reverted to correct behaviour. ([MDEV-37428](https://jira.mariadb.org/browse/MDEV-37428)) * mysqli silently trims each json\_arrayagg result to modulo 64KB ([MDEV-37835](https://jira.mariadb.org/browse/MDEV-37835)) ### Packaging * A tmpfiles file will now create /run/mysqld path on Debian/Ubuntu packaged distributions. ([MDEV-15502](https://jira.mariadb.org/browse/MDEV-15502)) * server cannot load client plugins on Debian ([MDEV-34744](https://jira.mariadb.org/browse/MDEV-34744)) * Previous systemd warnings in recent systemd versions about uninitialised environment variables have been corrected. ([MDEV-35904](https://jira.mariadb.org/browse/MDEV-35904)) * The PrivateDevices=false directive in the systemd service has been removed as it was an old kernel incompatibility that this directived worked around. With this, the MariaDB is restricted further. Those using InnoDB on raw devices will need to add an override for this. See