mysql-proxy would cause a segmentation fault if a connection was made from a client using the MySQL protocol 4.0 or earlier. (Bug#48641)

MySQL Proxy would load a configuration file with unsafe permissions, which could allow password information to be exposed through the configuration file. MySQL Proxy now refuses to load a file with unsafe permissions. (Bug#47589)

The supplied script ro-balance.lua had not been updated to use the resultset_is_needed and updated proxy.connection.dst.name structure. (Bug#47349, Bug#45408)

The line numbers provided in stack traces would be out by one line. (Bug#47348)

The supplied script active-transactions.lua had not been updated to use the new resultset_is_needed flag. (Bug#47345)

When submitting an address on the command line using --proxy-backend-addresses, the option would accept more than one address as an argument to the option. You should specify one --proxy-backend-addresses for each backend address. (Bug#47273)

MySQL Proxy would return the wrong version string internally from the proxy.PROXY_VERSION constant. (Bug#45996)

MySQL Proxy could stop accepting network packets if a large number of packets were sent to the proxy. The listen queue has been extended to allow a larger backlog. (Bug#45878, Bug#43278)

Due to a memory leak, memory usage for each uniqute connection to the proxy would increase, leading to very high consumption. (Bug#45272)

MySQL Proxy would fail to work with certain versions of MySQL, including MySQL 5.1.15, where a change in the MySQL protocol existed. (Bug#45167)

See also Bug#25371.

The supplied script rw-splitting.lua had not been updated to use the new resultset_is_needed flag or updated proxy.connections structure. (Bug#43424, Bug#42841, Bug#46141)

Logging to syslog with the use-log-syslog option did not work. (Bug#36431)

MySQL Proxy would raise an error when processing query packets larger than 16MB in size. (Bug#35202)