iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
MariaDB 12.3 is the current LTS feature series highlighted here, with its most notable additions spanning SQL and Oracle compatibility, replication, partitioning, and query optimization. MariaDB 12.2 added useful optimizer controls and JSON and metadata improvements, while 13.1 remains a rolling-release preview—not a stable production baseline.
What’s new in MariaDB 12.3?
MariaDB’s 12.3 changes cover more than SQL syntax: the release series also includes replication behavior, partitioning options, and join optimization. The capabilities below are documented in the MariaDB 12.3 changes and improvements overview. An optimization describes an implementation change; it does not guarantee a measurable gain for every workload.
SQL and Oracle compatibility
TO_DATE()adds an Oracle-compatible function for converting text to a date.- Cursors can be used with prepared statements, expanding how applications can execute and fetch results from prepared SQL.
SET PATHadds the SQL-standard statement for setting a path.IS JSONadds a SQL-standard way to test whether a value is valid JSON.UPDATEandDELETEcan read from a common table expression (CTE), allowing CTE-based queries to inform data changes.- A basic XML data type provides a dedicated type for XML values.
Replication changes
For replication configuration, 12.3 adds configurable defaults for MASTER_SSL_* settings used with CHANGE MASTER. It also fragments row-replication events that exceed max_packet_size, addressing oversized events. Binary-logging work is described as removing the need for syncing it; the overview does not quantify a performance gain.
Partitioning and query optimization
The series adds hash algorithms for PARTITION BY KEY, supports ordered scans over PARTITION BY RANGE, and makes LEFT JOIN reorderable by the optimizer. These changes matter most when they fit a particular schema and query plan; the feature overview does not establish a universal speedup.
What did MariaDB 12.2 add?
MariaDB 12.2 is a rolling-release series whose GA announcement highlights query-plan controls, JSON handling, and metadata improvements. It is useful context when comparing 12.2’s capabilities with the broader compatibility and replication work in 12.3.
| Feature | What it does | Who may find it useful |
|---|---|---|
[NO_]ROWID_FILTER optimizer hints |
Lets a query explicitly enable or disable the row-ID filter optimization. | Developers investigating or tuning query plans. |
[NO_]INDEX_MERGE optimizer hints |
Lets a query explicitly enable or disable index-merge behavior. | Teams that need more direct control over plan selection. |
| No previous 32-level limit for JSON functions | Removes the former nesting-depth ceiling for JSON functions. | Applications working with deeply nested JSON documents. |
INFORMATION_SCHEMA.TRIGGERED_UPDATE_COLUMNS |
Provides metadata for columns updated by triggers. | People inspecting trigger effects and database behavior. |
PARAMETER_DEFAULT in INFORMATION_SCHEMA.PARAMETERS |
Exposes stored-routine parameter defaults in metadata. | Tools and administrators examining routine definitions. |
These changes are described in MariaDB’s 12.2 GA announcement. MariaDB Product Manager Ralf Gebhardt characterized the optimizer work as making it smarter while retaining more granular control when needed; that is the project’s description, not an independent benchmark finding.
Is MariaDB 13.1 ready for production?
No: MariaDB.org described 13.1 as a rolling-release preview in its June 23, 2026 announcement. The preview includes 32 MDEVs—development items—with features and improvements across areas including SQL compatibility, JSON, tools, replication, observability, and storage engines. That count is not a performance metric or a statement that the features are stable. Treat 13.1 as preview material rather than a production feature baseline; see the MariaDB 13.1 preview announcement for its stated scope.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWhich MariaDB version should you upgrade to?
Choose based on the features you need, your support requirements, and the maturity of the release—not on a blanket assumption that the newest series is best for every deployment. MariaDB’s product overview says new LTS releases are announced yearly and that later patch versions do not add features, distinguishing a feature-series upgrade from routine patch maintenance. Release policy and schedules can change, so check the current MariaDB Server overview and release notes before planning an upgrade.
Support horizons reported in August 2026
In an announcement dated August 25, 2026, MariaDB.org listed Community maintenance horizons through 2029 for 12.3 and 11.4, and through 2028 for 11.8 and 10.11. The same announcement said Community Server 10.6 reached end of life on July 6, 2026, with 10.6.28 as its final release. These dates are the project’s published horizons in that announcement; confirm the current support table before making a long-term deployment decision.
Check the patch release, not just the series name
Patch status matters: MariaDB 12.3.1’s release notes identify it as an RC and warn against using it in production. A later MariaDB.org announcement, dated August 25, 2026, reports 12.3.3 among maintenance releases issued August 24. Consult the 12.3.1 release notes and the Q3 2026 maintenance announcement for those specific release details; verify the latest available stable patch and its notes before upgrading.
Quick Recap
Plan and validate the upgrade
- Identify the change you need. For SQL and Oracle compatibility or the 12.3 replication and partitioning work, evaluate 12.3. For 12.2 optimizer hints, deeper JSON handling, or the new metadata, check whether your target deployment supports that series.
- Confirm release status and support. Check the exact patch’s release notes and the current Community support information. Do not treat an RC or rolling preview as equivalent to a stable LTS release.
- Test in a representative environment. Exercise application queries, stored routines, triggers, replication, plugins, and configuration against the intended target version. Pay particular attention to features your application depends on and to query plans for important workloads.
- Deploy with a recovery plan. Schedule the change using your normal backup, rollback, and monitoring procedures; confirm expected application behavior after the upgrade.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
