MariaDB Server updates bring JSON fixes, replication tweaks, and storage engine patches
These MariaDB Server updates for versions 12.3, 11.8, 11.4, 10.11, and 10.6 skip the marketing fluff and focus entirely on query reliability, replication stability, and storage engine hardening. The release addresses several memory safety issues, tightens JSON parsing behavior, and cleans up packaging paths that have caused confusion for Debian and Red Hat administrators. Anyone running mixed version clusters or relying on heavy JSON workloads should check deployment pipelines before rolling out the new packages.
JSON handling and MariaDB Server updates
The development team finally stopped treating JSON like a guessing game. String to ENUM conversion now behaves predictably instead of silently dropping values into empty strings. JSON_EXTRACT no longer truncates results when pushed through derived tables, and JSON_SCHEMA_VALID finally returns the correct boolean for arrays of objects. The new IS JSON predicate adds a cleaner way to validate column types without triggering parser warnings. Database admins have watched plenty of production outages caused by trailing commas in JSON paths, and this release stops that assertion failure dead in its tracks. The optimizer also gets a reprieve from unnecessary filesort operations during derived table materialization, which translates to faster query execution on complex reports.
Replication and Galera cluster reliability
Replication has seen targeted fixes that matter for production environments running high write loads. The master heartbeat period parameter now accepts numeric values without rejecting them due to a plus sign. Sysadmins have seen this happen after a rushed config change when the parameter suddenly choked on valid numbers. Binlog session variable handling gets corrected to prevent state drift during failover events. Galera clusters benefit from a change that skips foreign key checks during initial sync transactions, which cuts down on unnecessary lock contention. Administrators managing multi-master setups should pay attention to the fix that finally allows slave_skip_errors to handle error code 1677. The replication parser also gets a clearer warning when a slave fails to execute its init query, which saves hours of troubleshooting for teams who have lost sync without knowing why.
Storage engine and Mroonga patches
The Mroonga full text storage engine receives several critical stability patches that address segmentation faults and index hang conditions. A NULL log file pointer no longer crashes the thread, and memory allocation for default tokenizer updates gets properly guarded. The team also stops the engine from hanging when it encounters invalid index flags, which prevents database downtime during automated maintenance windows. InnoDB gets a quieter upgrade path with improved auto increment check messages that actually explain what needs attention. Vector search functionality finally reports the correct index size in SHOW TABLE STATUS, which helps capacity planners avoid storage miscalculations.
Packaging, build system, and operational cleanup
Distribution packaging gets a long overdue cleanup that standardizes where PAM modules and systemd units land on disk. The debian build process stops installing files in legacy paths, and Red Hat RPM packages get a dedicated Galera server package to simplify repository management. Embedded server developers notice the mariadb.pc file rename, which removes ambiguity when linking against the C API. The feedback plugin switches to reading /etc/os-release for system identification, which makes version reporting more reliable across modern Linux distributions. Promoting GitHub stars in the server log feels like unnecessary noise for a production database, but at least the underlying build checks finally reject incompatible plugin modes before wasting cycles. Teams building from source will appreciate the configure time guard that stops broken configurations dead in their tracks.
Prioritizing stability over flashy features is exactly what this ecosystem needs right now. The JSON and replication fixes alone justify a quick review of deployment schedules. Check application logs for the specific error codes mentioned in the release notes, test the new packaging paths in a staging environment, and roll out the updates during the next maintenance window. The database keeps running smoother when you pay attention to the quiet improvements.
MariaDB Server 12.3, 11.8, 11.4, 10.11, 10.6 – May 2026’s releases: thank you for your contributions - MariaDB.org
On May… we have released an update of our 5 current LTS releases: These new releases contain a large amount of external contributions. The number of contributors is constantly growing, which is great! … Continue reading "MariaDB Server 12.3, 11.8, 11.4, 10.11, 10.6 – May 2026’s releases: thank you for your contributions"
Keep your queries clean and your clusters healthy.
