Release Notes for MariaDB MaxScale 2.5.13

Query Classifier crashes on UPDATE SELECTUPDATE SELECT statements. (MXS-3585)

When a client executed the EXPLAINEXPLAIN statement, the internal query classifier leaked a small amount of memory. (MXS-3566)

When a client executed a server-side prepared statement by sending a COM_STMT_EXECUTE packet with no metadata, the Read/Write Split Router (readwritesplit) required the request to be sent to the previous target server. (MXS-3565)

When a client attempted to authenticate using a specific authentication plugin, the plugin name was compared to the names of supported authentication plugins in a case sensitive manner. Starting with this release, plugin names are compared in a case insensitive manner. For example, both PAM and pam resolve to the pam authentication plugin. (MXS-3548)

When the max_slave_connections parameter was set to 0, the Read/Write Split Router (readwritesplit) refused all connections. Starting with this release, the router will only connect to the primary server when the max_slave_connections parameter is set to 0 (MXS-3536)

When a user-defined variable was referenced in a JOIN clause, the internal query classifier did not detect it, and MaxScale routed the query to the wrong target server. (MXS-3535)

When the syslog parameter was changed at runtime with maxctrl alter maxscale, the runtime value of the parameter was not changed. (MXS-3524)

When the maxlog parameter was disabled, MaxScale wrote messages to the MaxScale log during startup. (MXS-3479)

The CURRENT_TIMESTAMP() function can cause a parser error. (MXS-3589)

Read/Write Split router sending SET STATEMENT statements to replica servers on parser errors. (MXS-3586)

When using persistent connections, connection shutdowns right after creation are treated as an error. (MXS-3582)

Replicator component does not check node state for every operation. (MXS-3581)