The most recent release of MariaDB Enterprise Server 11.4 is: 11.4.12-9
Download Enterprise Server 11.4.12-9
{% endhint %} MariaDB Enterprise Server 11.4.5-3 is a Stable (GA) maintenance release of [MariaDB Enterprise Server](https://github.com/mariadb-corporation/docs-release-notes/blob/test/kb/en/mariadb-enterprise-server/README.md) 11.4. This release includes a variety of fixes. MariaDB Enterprise Server 11.4.5-3 was released on **19 Mar 2025**. ## Fixed Security Vulnerabilities | CVE (with cve.org link) | CVSS base score (v3.1) | | ------------------------------------------------------------------------------- | ---------------------- | | [CVE-2025-21490](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21490) | 4.9 | [Full list of Fixed Security Vulnerabilities in MariaDB Enterprise Server](/docs/server/security/cve/enterprise-server.md) ## Changes in Storage Engines * This release incorporates MariaDB ColumnStore engine version [23.10.3](/docs/release-notes/columnstore/23.10/23.10.3.md). ## Backports #### Vector Search The vector search capability has now been added to the MariaDB Enterprise Server 11.4 release. The linked [blog post](https://mariadb.com/resources/blog/mariadb-vector-preview-is-out/) explains the idea of the new vector search feature in detail. ([MENT-2233](https://jira.mariadb.org/browse/MENT-2233)) #### Vector Embeddings Vector embeddings are numerical representations `[0.2, -0.5, 0.8, 0.1, ...]` that capture semantic meaning or features of data in a multi-dimensional space. The embedding transforms simple to complex data such as text, images, audio, or video into a series of numbers (a vector) where similar items are positioned together in the multi-dimensional vector space. For example, a word embedding of the word "dog" would be close in a vector embedding space to the word "puppy", whereas "dog" would not be close to the word "airplane". The embedding representation can be used in similarity search, recommendation systems, or more generally in traditional AI/ML systems and GenAI systems. #### New Data Type VECTOR(N) A new data type `VECTOR(N)` has been added to represent the vector column, where N is the number of dimensions.\ Example: ```sql CREATE TABLE myVectorSearch ( id INT PRIMARY KEY, v VECTOR(5) NOT NULL, VECTOR INDEX (v) ); ``` #### Conversion Functions `VEC_FromText()` converts a text representation of the vector (a json array of numbers) to a vector (little-endian IEEE float sequence of bytes, 4 bytes per float). Example: ```sql SELECT hex(vec_fromtext('[1,2,3]')); ``` ``` +------------------------------+ | hex(vec_fromtext('[1,2,3]')) | +------------------------------+ | 0000803F0000004000004040 | +------------------------------+ ``` `VEC_ToText()` converts a binary vector into a json array of numbers (floats).\ Example: ```sql SELECT VEC_ToText(x'e360d63ebe554f3fcdbc523f4522193f5236083d'); ``` ``` +---------------------------------------------------------+ | VEC_ToText(x'e360d63ebe554f3fcdbc523f4522193f5236083d') | +---------------------------------------------------------+ | [0.418708,0.809902,0.823193,0.598179,0.033255] | +---------------------------------------------------------+ ``` #### Comparison Functions Comparing vectors, calculating how close they are, is the key functionality needed by an application working with vector search. Two functions exist for calculating the distance between vectors. Which one to use depends on the application and on how the vectors were generated. `VEC_DISTANCE_EUCLIDEAN()` takes two vectors and computes the straight line (L2) Euclidean distance between two multi-dimensional points in the vector space Example: ```sql INSERT INTO v VALUES (1, x'e360d63ebe554f3fcdbc523f4522193f5236083d'), (2, x'f511303f72224a3fdd05fe3eb22a133ffae86a3f'), (3,x'f09baa3ea172763f123def3e0c7fe53e288bf33e'), (4,x'b97a523f2a193e3eb4f62e3f2d23583e9dd60d3f'), (5,x'f7c5df3e984b2b3e65e59d3d7376db3eac63773e'), (6,x'de01453ffa486d3f10aa4d3fdd66813c71cb163f'), (7,x'76edfc3e4b57243f10f8423fb158713f020bda3e'), (8,x'56926c3fdf098d3e2c8c5e3d1ad4953daa9d0b3e'), (9,x'7b713f3e5258323f80d1113d673b2b3f66e3583f'), (10,x'6ca1d43e9df91b3fe580da3e1c247d3f147cf33e'); ``` ```sql SELECT id FROM v ORDER BY VEC_DISTANCE_EUCLIDEAN(v, x'6ca1d43e9df91b3fe580da3e1c247d3f147cf33e'); ``` ``` +----+ | id | +----+ | 10 | | 7 | | 3 | | 9 | | 2 | | 1 | | 5 | | 4 | | 6 | | 8 | +----+ ``` `VEC_DISTANCE_COSINE()` measures the cosine distance between two vectors in a multi-dimensional vector space Example: ```sql SELECT VEC_DISTANCE_COSINE(VEC_FROMTEXT('[1,2,3]'), VEC_FROMTEXT('[3,5,7]')); ``` ``` +-----------------------------------------------------------------------+ | VEC_DISTANCE_COSINE(VEC_FROMTEXT('[1,2,3]'), VEC_FROMTEXT('[3,5,7]')) | +-----------------------------------------------------------------------+ | 0.00258509695694209 | +-----------------------------------------------------------------------+ ``` #### Configuration Options The vector search feature requires some [new system variables](/docs/server/reference/sql-structure/vectors/vector-system-variables.md) for controlling the general behavior. Four new system variables have been added: * `mhnsw_max_cache_size` - Upper limit for one MHNSW vector index cache * `mhnsw_default_distance` - Default value for the DISTANCE vector index option * `mhnsw_default_m` - Default value for the M vector index option * `mhnsw_ef_search` - Minimal number of result candidates to look for in the vector index for ORDER BY ... LIMIT N queries. ## Notable Changes * Starting with this release we generate a Software Bill of Materials (SBOM) JSON file provided in the downloads archive, which can be reached from the "All Files" link on the MariaDB Enterprise Server downloads page ([MENT-2234](https://jira.mariadb.org/browse/MENT-2234)) * New parameter `--skip-freed-pages` for `Innochecksum`. Use this parameter to not get freed undo logs reported as existing undo log pages. ([MDEV-35394](https://jira.mariadb.org/browse/MDEV-35394)) * Galera protocol versions are now shown by show status - change available with installation of galera library 26.4.21+ ([MDEV-35505](https://jira.mariadb.org/browse/MDEV-35505)) * MariaDB now supports MySQL 8.0 binlog events, including `PARTIAL_UPDATE_ROWS_EVENT`, `TRANSACTION_PAYLOAD_EVENT`, and `HEARTBEAT_LOG_EVENT_V2`. ([MDEV-35643](https://jira.mariadb.org/browse/MDEV-35643)) * InnoDB deadlock output query length increased to improve visibility of deadlocked statements. ([MDEV-32576](https://jira.mariadb.org/browse/MDEV-32576)) * [Galera](https://github.com/mariadb-corporation/docs-release-notes/blob/test/kb/en/galera-cluster/README.md) updated to [26.4.21](/docs/release-notes/galera-cluster/26.4/26.4.21.md) * NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated ## Issues Fixed ### Can result in data loss * Fix incorrect writing of timestamp into binary log, causing discrepancy upon binlog replaying ([MDEV-31761](https://jira.mariadb.org/browse/MDEV-31761)) * Fix trigger created with "`CREATE TRIGGER` table1\_after\_insert `AFTER INSERT`" which is adding rows to another table using "`FOR EACH ROW insert into table2(`id`,` name`) values (NEW.`id`, NEW.`name`);`" that did not work correctly when if bulk inserts are used by the application. Only the first row of the bulk insert would be added to the table ([MDEV-34958](https://jira.mariadb.org/browse/MDEV-34958)) * History is now stored on the same partitions on different Galera nodes when system versioning is enabled ([MDEV-35096](https://jira.mariadb.org/browse/MDEV-35096)) * Fix assertion falilure and possible index corruption with unique key and nopad collation without `DESC` or `HASH` keys ([MDEV-30111](https://jira.mariadb.org/browse/MDEV-30111)) ### Can result in hang or crash * Fix client crash the command after client sets character set to utf32 ([MDEV-34090](https://jira.mariadb.org/browse/MDEV-34090)) * Fix possible crash where server could not construct a geomery object from the input ([MDEV-33987](https://jira.mariadb.org/browse/MDEV-33987)) * Fix possible InnoDB hang while running out of buffer pool ([MDEV-35409](https://jira.mariadb.org/browse/MDEV-35409)) * Fix possible Spider thread hang in 'Update' state on 2nd INSERT ([MDEV-35064](https://jira.mariadb.org/browse/MDEV-35064)) * After changing the table definition for the system table '`mysql.servers`', a following execution of `CREATE SERVER` would previously lead to a server crash. * NOTE: System tables should never be modified by a user anyhow ([MDEV-33783](https://jira.mariadb.org/browse/MDEV-33783)) * FIx streaming replication transaction crash with innodb\_snapshot\_isolation ([MDEV-35281](https://jira.mariadb.org/browse/MDEV-35281)) * Fix sporadic failure of async replication on Galera async replica nodes with parallel replication enabled ([MDEV-35465](https://jira.mariadb.org/browse/MDEV-35465)) * Fix failing assertion causing disruption and replication failure ([MDEV-24035](https://jira.mariadb.org/browse/MDEV-24035)) * Fix possible failure of wsrep\_sst\_rsync SST script if user specified aria\_log\_dir\_path different from default data directory ([MDEV-35387](https://jira.mariadb.org/browse/MDEV-35387)) * Fix connection hang after query on a partitioned table with `UNION` and `LIMIT ROWS EXAMINED` ([MDEV-35571](https://jira.mariadb.org/browse/MDEV-35571)) * Fix server crash in `get_sort_by_table`/`make_join_statistics` after `INSERT` into a view with `ORDER BY` ([MDEV-29935](https://jira.mariadb.org/browse/MDEV-29935)) * Fix possible hang during `CREATE TABLE...SELECT` error handling, especially with innodb\_snapshot\_isolation enabled ([MDEV-35647](https://jira.mariadb.org/browse/MDEV-35647)) * Fix incorrect locking order of `LOCK_log`/`LOCK_commit_ordered`, and `LOCK_global_system_variables` ([MDEV-29744](https://jira.mariadb.org/browse/MDEV-29744)) * Fix possible memory leak on `SHUTDOWN` ([MDEV-35326](https://jira.mariadb.org/browse/MDEV-35326)) * Fix possible memory leak while shutting down server after installing the `auth_gssapi` plugin ([MDEV-35575](https://jira.mariadb.org/browse/MDEV-35575)) * Fix possible crash on `DELETE` from a `HEAP` table ([MDEV-22695](https://jira.mariadb.org/browse/MDEV-22695)) * Fix possible server crash when using `INSERT DELAYED` on tables with virtual columns. ([MDEV-26891](https://jira.mariadb.org/browse/MDEV-26891)) * Fix possible crash during index traversal using `tree_search_next`. ([MDEV-28130](https://jira.mariadb.org/browse/MDEV-28130)) * Fix possible hang or crash during InnoDB purge with `HASH` indexes during `ALTER TABLE` ([MDEV-25654](https://jira.mariadb.org/browse/MDEV-25654)) * Fix possible hang or crash where zero offset applied to null pointer ([MDEV-35864](https://jira.mariadb.org/browse/MDEV-35864)) * Fix possible crash on bootup in `spider_sys_open_table` ([MDEV-32822](https://jira.mariadb.org/browse/MDEV-32822), [MDEV-34302](https://jira.mariadb.org/browse/MDEV-34302), [MDEV-34925](https://jira.mariadb.org/browse/MDEV-34925)) * Fix possible Spider crash or hang when the first byte of a connection key is changed ([MDEV-34849](https://jira.mariadb.org/browse/MDEV-34849)) * Fix possible runtime error caused by `XA RECOVER` applying a zero offset to a null pointer ([MDEV-35549](https://jira.mariadb.org/browse/MDEV-35549)) * Fix assertion failure on cascading foreign key update of table with `vcol` index in parent ([MDEV-29182](https://jira.mariadb.org/browse/MDEV-29182)) * FIx assertion failure where `CURRENT_USER` was not correctly copied during condition pushdown ([MDEV-35090](https://jira.mariadb.org/browse/MDEV-35090)) * Fix cluster node hang during shutdown if threadpool is used ([MDEV-35710](https://jira.mariadb.org/browse/MDEV-35710)) * Calling a stored routine that executes a join on three or more tables and referencing not-existent column name in the `USING` clause could previously result in a crash on its second invocation. ([MDEV-24935](https://jira.mariadb.org/browse/MDEV-24935)) * Fix possible assertion failure when Galera cluster is in 'split-brain' state due to loss of communication between nodes (fix requires Galera library 26.4.21+) ([MENT-2175](https://jira.mariadb.org/browse/MENT-2175)) * Fix assertion failure when executing `XA PREPARE` (and possibly other XA statements) on Galera cluster nodes ([MENT-2212](https://jira.mariadb.org/browse/MENT-2212)) * Fix assertion failure when executing `XA` statements on Galera cluster nodes ([MENT-2214](https://jira.mariadb.org/browse/MENT-2214)) * In rare cases, an `ALTER TABLE` or other operation could previously hang when using `NBO` mode on a cluster with very low network latencies (for example, when both nodes are running on the same physical machine) ([MENT-2215](https://jira.mariadb.org/browse/MENT-2215)) * MariaDB Cluster and `ALTER INPLACE` running in Total Order Isolation (`wsrep_OSU_method=TOI`) now correctly abort a `DML INSERT` operation in InnoDB ([MDEV-33064](https://jira.mariadb.org/browse/MDEV-33064)) * Fix possible crash in `wsrep_check_sequence` ([MDEV-33245](https://jira.mariadb.org/browse/MDEV-33245)) ### Can result in unexpected behaviour * Fix sporadic reporting of success when a deadlock error occurs under `--ps-protocol BF` aborted transaction ([MDEV-35446](https://jira.mariadb.org/browse/MDEV-35446)) * Fix rare cases where binlog entries could receive incorrect timestamps on secondary nodes of a Galera cluster, potentially impacting replication accuracy ([MDEV-35157](https://jira.mariadb.org/browse/MDEV-35157)) * For an authentication with the ed25519 authentication plugin the password of the `CREATE USER` statement is now masked in the audit log ([MDEV-35507](https://jira.mariadb.org/browse/MDEV-35507)) * MariaDB Audit now detects all DCLs forms for masking a password ([MDEV-35522](https://jira.mariadb.org/browse/MDEV-35522)) * Fix potential issue in secondary Index with `ROW_FORMAT=COMPRESSED` and Change buffering enabled ([MDEV-35679](https://jira.mariadb.org/browse/MDEV-35679)) * `sql_mode='NO_UNSIGNED_SUBTRACTION'` now works for multiple unsigned integers ([MDEV-35651](https://jira.mariadb.org/browse/MDEV-35651)) * Fix doublewrite recovery of `innodb_checksum_algorithm=full_crc32` encrypted pages ([MDEV-34898](https://jira.mariadb.org/browse/MDEV-34898)) * `START TRANSACTION`, when triggering an implicit commit as a `COMMIT` or `ROLLBACK` has not been executed before, now resets optional characteristics added to the last `START TRANSACTION` command ([MDEV-35335](https://jira.mariadb.org/browse/MDEV-35335)) * `mariadb-binlog` can now correctly process more than one logfile when `--stop-datetime` is specified ([MDEV-35528](https://jira.mariadb.org/browse/MDEV-35528)) * Rows in table `mysql.gtid_slave_pos` are now correctly deleted on Galera nodes when `wsrep_gtid_mode = 1` is used, which previously lead to wrong information about replica delays ([MDEV-34924](https://jira.mariadb.org/browse/MDEV-34924)) * `EXCHANGE PARTITION` now works for tables with unique blobs ([MDEV-35612](https://jira.mariadb.org/browse/MDEV-35612)) * Fix issue where functions in default values in tables with certain character sets could break `SHOW CREATE` and `mariadb-dump` ([MDEV-29968](https://jira.mariadb.org/browse/MDEV-29968)) * Setting `pseudo_thread_id` to a value exceeding 4 bytes previously resulted in truncation when written to the binary log ([MDEV-35646](https://jira.mariadb.org/browse/MDEV-35646)) * A `BEFORE INSERT` Trigger previously returned with error "`Field 'xxx' doesn't have a default value`", if a `NULL` value was added for a column defined `NOT NULL` without explicit value and no `DEFAULT` specified ([MDEV-19761](https://jira.mariadb.org/browse/MDEV-19761)) * Undefined behavior could occur when attempting to perform `INSERT DELAYED` on a Galera cluster node. ([MDEV-35852](https://jira.mariadb.org/browse/MDEV-35852)) * Fix issue where `ON UPDATE SET NULL` could not be specified on a `NOT NULL` column ([MDEV-35445](https://jira.mariadb.org/browse/MDEV-35445)) * `algorithm = instant` can now correctly be used if a table has partitions and one tries to change a column with an index which is not the partitions key. This previously gave error "`ERROR 1846 (0A000): ALGORITHM=INSTANT is not supported. Reason: ADD INDEX. Try ALGORITHM=NOCOPY`" ([MDEV-34813](https://jira.mariadb.org/browse/MDEV-34813)) * Fix issue where `DROP TABLE` on child and `UPDATE` of parent table can cause a metadata lock `BF-BF` conflict when applied concurrently. ([MDEV-35018](https://jira.mariadb.org/browse/MDEV-35018)) * Can now correctly add a foreign key on a table with a long `UNIQUE` multi-column index that contains a foreign key as a prefix ([MDEV-33658](https://jira.mariadb.org/browse/MDEV-33658)) * Fix possibly wrong result using a degenerated subquery `(SELECT