MariaDB MaxScale 2.5.13 Release Notes -- 2021-06-04

You are viewing an old version of this article. View the current version here.

MariaDB MaxScale 2.5.13 Release Notes -- 2021-06-04

Release 2.5.13 is a GA release.

This document describes the changes in release 2.5.13, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-3566 EXPLAIN leaks memory
  • MXS-3565 COM_STMT_EXECUTE target selection is too restrictive when no metadata is provided
  • MXS-3548 Plugin name comparison is case-sensitive
  • MXS-3538 Removal of authenticator_options is not documented in upgrade documents
  • MXS-3536 max_slave_connections=0 doesn't work as expected
  • MXS-3535 user variable is not collected if it's in join clause
  • MXS-3533 MaxScale doesn't advertise the SESSION_TRACK capability
  • MXS-3529 Maxscale is not compatible with the latest cmake 3.20
  • MXS-3528 Maxscale source repo contains old boost-1.73.0.tar.gz which is not buildable with latest cmake on ARM
  • MXS-3524 alter syslog is not supported during runtime
  • MXS-3479 Disabling maxlog doesn't fully prevent it from being written to
  • MXS-3589 qc_sqlite handles current_timestamp etc. explicitly
  • MXS-3586 Maxscale tries to execute write statement on slave
  • MXS-3585 query classifier crashes after upgrade from 2.5.11 to 2.5.12
  • MXS-3582 [readwritesplit] Failed to execute session command
  • MXS-3581 Replicator component doesn't check node state for every operation

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for supported the Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.