Release Notes for MariaDB Xpand 6.1.2

Group changes with ongoing writes to columnar indexes can cause the columnar indexes to become corrupted. (XPAND-36922)

Scaling out using more nodes than currently in quorum overwrites the system catalog. (XPAND-37129)

Setting internode_timeout_ms to a too-low value (for example 100ms) can prevent a cluster from forming. (XPAND-37241)

Rarely, when executing a soft group change the group management protocol encounters a race condition and causes a hard group change. (XPAND-37087)

Using a large number of values in COALESCE() can result in a crash. (XPAND-37068)

When a query compilation triggers a recompile, and the query optimizer finds an empty expression, it can result in a crash. (XPAND-36785)

Generating a debug dump can cause a crash. (XPAND-36701)

When using the Xpand Query Optimizer, sarged plans are not always encouraged over non-sarged plans. (XPAND-36788)

During a group change, excess messaging could occur. (XPAND-37216)

During upgrades, lz4 package dependencies are not checked.

Flushing the Query Plan Cache (QPC) can be over-aggressive leading to more query re-compilation and resulting in slightly decreased performance. (XPAND-37036)

URIs can be incorrectly encoded when using backup/restore from S3. (XPAND-37091)

The Host Anomaly Detector incorrectly generates error messages if non-default log locations are configured. (XPAND-36760)