MariaDB Foundation posted a new MariaDB 13.1 preview feature note for database admins who run JSON, TEXT, BLOB, or GEOMETRY-heavy workloads. The practical change is that the HEAP engine, also known as the MEMORY engine, can support those column types for more temporary-table cases instead of forcing a move to disk because of the column type alone.
This is not a production emergency and it is not a security patch. Treat it as a testing item for staging labs, performance reviews, and upgrade planning around MariaDB 13.1 preview.
What Changed
MariaDB says the HEAP engine previously could not handle BLOB or TEXT columns. JSON and GEOMETRY were affected too because MariaDB represents those internally in a BLOB-like way. When an internal temporary table needed one of those values, the server could fall back to a disk-based temporary table even when the data was small enough to fit in memory.
With the MariaDB 13.1 preview work, more internal temporary tables can stay in memory when they fit within the configured limits. That matters for workloads that use:
- JSON columns or JSON-like application data
- TEXT and BLOB values in reporting queries
- GEOMETRY or spatial data
- GROUP BY, DISTINCT, UNION, subqueries, or common table expressions
Who Should Pay Attention
Hosting providers and site owners do not need to move production databases because of this announcement. The useful audience is teams already testing MariaDB 13.1 preview or maintaining applications where temporary-table performance is a known pain point.
For WordPress and WooCommerce stacks, this is mostly a future-looking database note. Many sites will not notice it directly. Larger custom plugins, analytics tables, reporting dashboards, booking systems, search layers, and product/catalog integrations are more likely to benefit from testing.
Safe Testing Checklist
- Keep production on the currently supported database release until your normal compatibility policy says otherwise.
- Use a staging database copy, not the live production database, for MariaDB 13.1 preview checks.
- Pick slow queries that use JSON, TEXT, BLOB, GEOMETRY, GROUP BY, DISTINCT, UNION, subqueries, or CTEs.
- Compare temporary-table behavior and query timing against your current MariaDB version.
- Check application-level behavior, not only raw query timing. Admin dashboards, reports, exports, and scheduled jobs should still return the same results.
- Record any difference that matters and send useful feedback upstream while 13.1 is still in preview.
Bottom Line
This is a good staging-lab item for database-heavy hosting customers. If your application regularly spills JSON, TEXT, BLOB, or GEOMETRY temporary tables to disk, MariaDB 13.1 preview is worth testing. If your site runs ordinary WordPress content and store queries without known database pain, keep this on the upgrade-planning list rather than the urgent maintenance list.
Sources Checked
Validation used the July 10, 2026 MariaDB Foundation post, the linked MariaDB Jira issue MDEV-38975, and the linked MariaDB Server pull request. Claims above are limited to BLOB, TEXT, JSON, and GEOMETRY testing and planning guidance for the MariaDB 13.1 preview feature.