This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-24. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB MaxScale 2.4.5 Release Notes -- 2019-12-21

MariaDB MaxScale 2.4.5 Release Notes -- 2019-12-21

Release 2.4.5 is a GA release.

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

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

New Features

  • MXS-2785 Allow database renaming in binlogfilter

Bug fixes

  • MXS-2813 maxctl shows password in clear text
  • MXS-2809 2.4 configuration still contains links to v2.3 documentation
  • MXS-2803 Hang with readconnroute and persistent connections
  • MXS-2802 COM_RESET_CONNECTION is treated as a write
  • MXS-2794 Reloading of users is not logged
  • MXS-2788 Masking filter performs case-sensitive checks against unquoted case-insensitive identifiers in function calls and WHERE clauses
  • MXS-2782 Wrong thread id causes MaxScale to crash.
  • MXS-2776 Binlog filter skipping commit when writing to ColumnStore
  • MXS-2775 Document that a crashed master can break auto_rejoin with semisynchronous replication
  • MXS-2498 MaxScale not routing TEMPORARY TABLE reading to MASTER

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.

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.