> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/release-notes/community-server/13.0/13.0.1.md).
# MariaDB 13.0.1 Release Notes
Download Release Notes Changelog Overview of 13.0
**Release date:** 29 May 2026
{% hint style="danger" %} **Do not use non-stable (non-GA) releases in production!**
{% endhint %}
MariaDB 13.0 is a [rolling release](/docs/release-notes/community-server/about/release-model.md). It is an evolution of [MariaDB 12.3](/docs/release-notes/community-server/12.3/mariadb-12.3-changes-and-improvements.md) with several entirely new features.
MariaDB 13.0.1 is a [***Release Candidate (RC)***](/docs/release-notes/community-server/about/release-criteria.md) release.
{% hint style="success" %}
**For an overview of MariaDB 13.0 see the** [**MariaDB 13.0 Changes & Improvements**](/docs/release-notes/community-server/13.0/mariadb-13.0-changes-and-improvements.md) **page.**
{% endhint %}
Thanks, and enjoy MariaDB!
## New Features
* Add support for `TYPE .. IS REF CURSOR` ([MDEV-10152](https://jira.mariadb.org/browse/MDEV-10152))
* One can specify timestamp format for the audit plugin log ([MDEV-18386](https://jira.mariadb.org/browse/MDEV-18386))
* Atomic `CREATE OR REPLACE TABLE` ([MDEV-25292](https://jira.mariadb.org/browse/MDEV-25292))
* `INFORMATON_SCHEMA.SYSTEM_VARIABLES` shows if a variable is deprecated ([MDEV-35369](https://jira.mariadb.org/browse/MDEV-35369))
* `INFORMATON_SCHEMA.STATISTICS` and `INFORMATON_SCHEMA.COLUMNS` shows engine specific create options ([MDEV-36444](https://jira.mariadb.org/browse/MDEV-36444))
* Optimizer Trace includes used optimizer statistics ([MDEV-36511](https://jira.mariadb.org/browse/MDEV-36511))
* New `innodb_log_archive` variable makes InnoDB preserve the write-ahead log in a continuous sequence of files instead of overwriting a ring buffer, enabling point-in-time recovery and incremental backups ([MDEV-37949](https://jira.mariadb.org/browse/MDEV-37949))
* New `QB_NAME()` optimizer hint ([MDEV-38045](https://jira.mariadb.org/browse/MDEV-38045))
* Support `RECORD` in routine parameters and function `RETURN` clause ([MDEV-38768](https://jira.mariadb.org/browse/MDEV-38768))
* Reversed executable comments ([MDEV-7381](https://jira.mariadb.org/browse/MDEV-7381))
## Notable Items
* `CHANGE MASTER` now resets `Master_Server_Id` in `SHOW SLAVES STATUS` ([MDEV-15327](https://jira.mariadb.org/browse/MDEV-15327))
* Faster unique indexes over `CHAR` columns in MEMORY tables (incl. temporary tables) ([MDEV-21543](https://jira.mariadb.org/browse/MDEV-21543))
* `PERFORMANCE_SCHEMA` now uses `XXH3_128` hash for digest. Looks like MD5, but much faster and no problems in FIPS mode. ([MDEV-31669](https://jira.mariadb.org/browse/MDEV-31669))
* `binlog_row_event_max_size` default value was increased to 64k ([MDEV-37608](https://jira.mariadb.org/browse/MDEV-37608))
* `default_master_connection` can now be set on global level ([MDEV-9247](https://jira.mariadb.org/browse/MDEV-9247))
*This page is licensed: CC BY-SA / Gnu FDL*
{% @marketo/form formid="4316" formId="4316" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://mariadb.com/docs/release-notes/community-server/13.0/13.0.1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.