What MariaDB/server shipped

This week: ANY_VALUE() added, OPTIMIZE TABLE stops growing tables, mariabackup SST backup data authenticated, plugin_dir from backup-my.cnf no longer trusted, crash-safe innodb_log_archive, and recovery no longer hangs on a corrupted tablespace.

Changes this week in MariaDB server. ANY_VALUE() is added as a SQL:2023 T626 feature. OPTIMIZE TABLE no longer makes tables grow, because bulk page allocation now tries adjacent pages. The mariabackup SST backup-data stream is authenticated, and mariabackup --prepare no longer trusts plugin_dir from backup-my.cnf, which can arrive over an untrusted channel. Setting GLOBAL innodb_log_archive=ON is now crash safe. Recovery no longer hangs when a system or undo tablespace page is corrupted. TRUNCATE TABLE hitting a foreign key again returns ER_TRUNCATE_ILLEGAL_FK, which application frameworks rely on. mariadb-binlog date options now handle values outside the TIMESTAMP range.

Changes this week: DELETE IGNORE with FK cascades on FULLTEXT tables no longer trips an InnoDB assertion; iterated partition scans no longer loop forever; deletes by key prefix in MEMORY BTREE tables no longer skip rows; OFFSET inside IN subqueries is now refused instead of retur

This week's changes were mostly fixes for problems users hit in production. InnoDB no longer asserts on DELETE IGNORE with foreign key cascades on tables with FULLTEXT indexes, iterated partition index scans no longer loop forever, and deletes by key prefix in MEMORY BTREE tables no longer skip rows. OFFSET inside IN, ALL and ANY subqueries is rejected rather than silently returning wrong results, and deeply nested boolean FULLTEXT queries no longer overflow the stack when freed. Elsewhere, read views after a table reload no longer see wrong data after ALTER TABLE, a crash on the second run of a stored procedure changing a view is fixed, and Galera keeps its gtid domain id setting across a pc.recovery restart.

This week: CIDR notation in user account host names, correct bulk insert values with parameter-dependent subqueries, no more index corruption on versioned InnoDB updates, and AES_ENCRYPT()/KDF() fixed on OpenSSL 4.0. ROW_NUMBER and TO_DATE are usable as names again.

Changes in MariaDB this week: user account host names can now be written in CIDR notation, such as '192.168.0.0/24', and are normalized to the netmask form. Optimized array binding INSERT and REPLACE now execute once per parameter set when a subquery depends on those parameters, fixing wrong values in bulk inserts. UPDATE on versioned InnoDB tables no longer corrupts indexes, and an UPDATE with several indexed virtual columns no longer overruns the update buffer. AES_ENCRYPT() and KDF() work again on OpenSSL 4.0. ROW_NUMBER and TO_DATE were relaxed from reserved keywords so they can be used as identifiers, and STR_TO_DATE() no longer reads past the end of its input.

This week: JSON_OVERLAPS and JSON_TABLE BIT fixes for wrong results, no more crash selecting DuckDB TIME values, a range optimizer stack overrun fix, an AUTO_INCREMENT race in partitioned tables, and a new --validate-config option that checks configuration without starting the se

This week's MariaDB server work fixes several wrong results and crashes: JSON_OVERLAPS treating unequal nested arrays as equal, JSON_TABLE returning wrong BIT values, a server crash when selecting DuckDB TIME values, a stack overrun in the range optimizer on compound keys with many parts, and an AUTO_INCREMENT race in partitioned tables. Locking reads on DuckDB tables are now rejected with a clear unsupported error instead of failing inside the embedded engine. There is also a new --validate-config option that checks configuration from files and the command line and exits without starting the server, and fixes in CONNECT XmlDB buffer handling, BINLOG statements in triggers, and Galera.

This week: Ctrl-C now stops tab separated output in the mariadb client, HANDLER READ checks column privileges, replication filter variables respect default_master_connection, and view statements no longer get pushed down by FederatedX. Docs URLs updated across branches.

This week's changes: the mariadb client now interrupts tab separated result output on Ctrl-C. HANDLER READ performs column privilege checks and reopen validates privileges. Replication filter system variables respect the default_master_connection qualifier. Multi-table UPDATE and DELETE that use a view are no longer pushed down to a remote server. Help table documentation URLs were updated across supported branches to point to MariaDB Documentation. Several crash fixes landed, including a fix for converting an IN predicate with a nested ROW into an IN subquery, and wsrep_sync_wait now works after COM_CHANGE_USER and COM_RESET_CONNECTION.

MariaDB fixes: prepared statement MATCH crashes, JSON array bounds errors, FederatedX DELETE issues, DATE_FORMAT with negative TIME, decimal overflow assertions, CONCAT dropping arguments, RISC-V CRC-32C acceleration, versioned DELETE index bugs, window function NULL handling.

This week's MariaDB update addresses 10+ critical issues: fixed server crashes in prepared statements with MATCH clauses, corrected ASAN errors in JSON operations, resolved FederatedX DELETE problems, fixed DATE_FORMAT truncation, prevented decimal overflow assertions, repaired CONCAT argument loss, added RISC-V Zvbc CRC-32C acceleration, corrected system-versioned DELETE index behavior, and fixed window function NULL handling in bit aggregates.

MariaDB weekly: Fixed multi-table DELETE crashes, partitioned table query results, buffer overflows in CONNECT and CREATE DATABASE, instant ALTER TABLE corruption, and PROXY protocol security. Added RISC-V CRC32C acceleration.

MariaDB weekly digest: This week's fixes address critical stability and security issues. We resolved crashes in multi-table DELETE with window functions, incorrect results in partitioned table descending scans, and buffer overflows in the CONNECT engine. Security improvements defer PROXY protocol validation until after SSL handshake. Virtual column corruption during instant ALTER TABLE rollback is fixed. We also added hardware-accelerated CRC32C for RISC-V systems and improved sys schema upgrade handling to preserve user grants.

MariaDB 13.1.1 RC and 13.0.2 are now available. This week brings FILTER clause support for aggregates, fixes for Galera applier hangs with UUID/INET types, and improved error reporting in storage engine operations.

Two releases this week: MariaDB Community Server 13.1.1 RC and 13.0.2. Notable improvements include SQL-standard FILTER clause for aggregate functions, resolution of Galera applier hangs with UUID/INET4/INET6 foreign keys, elimination of spurious gap locks in UPDATE...IN(SELECT), and fixes to error handling in replication and recovery scenarios. These updates address both new functionality requests and critical stability issues.