Software 44223 Published by

The MariaDB team has opened testing for version 13.0 with a focus on practical SQL improvements and better backup reliability. New procedural language features like REF CURSOR support give developers more control while a new optimizer hint helps when execution plans go off track. The standout addition is InnoDB Log Archive which saves WAL history instead of overwriting old redo logs to make recovery smoother during long backups. 



MariaDB 13.0 Preview Adds Practical Backup Fixes and SQL Control for Power Users

The developers behind the open-source database have released a preview of version 13.0, bringing fresh tools for backup handling and query tuning. This release targets pain points that usually show up during late-night troubleshooting sessions or when optimizing complex routines. Readers will see how specific engine improvements change the way data is archived without forcing a full reinstall.

SQL changes that actually matter for developers working with MariaDB 13.0 Preview

The new procedural language capabilities look small on paper but they fix real friction points in daily work. Support for TYPE IS REF CURSOR and RECORD in routine parameters allows for cleaner code when moving between stored procedures. A new optimizer hint called "QB_NAME" gives control back to the developer when execution plans go off the rails. There are also reversed executable comments which sound obscure until you need them for specific tooling compatibility. These updates do not add flashy bells and whistles but they improve expressiveness and broaden compatibility for existing scripts.

Why the InnoDB Log Archive feature solves a common backup headache in MariaDB 13.0 Preview

One of the more useful additions is the innodb_log_archive variable that preserves WAL history instead of overwriting old redo log entries. Experienced admins know backups fail or take forever when the circular buffer wraps around during long transactions. The setting allows enabling this feature at runtime to keep those archived files on the filesystem for later recovery steps. The variable "innodb_lsn_archived" helps track exactly which part of the history is available for restore operations. Metadata improvements also help when things break since INFORMATION_SCHEMA.SYSTEM_VARIABLES now flags deprecated options so teams do not waste time chasing warnings in production logs. Performance schema uses XXH3_128 digests which might seem technical but helps with stability during heavy load monitoring.

MariaDB 13.0 Preview Now Available

The new preview release of MariaDB is now available. We’re looking forward to hearing what you think. Your feedback is important to us during these previews. And of course, we want to thank all the developers who already contributed and encourage others to contribute to MariaDB.

MariaDB 13.0 Preview Now Available - MariaDB.org