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

The port number reported in proxy.connection.client.address would be reported incorrectly. (Bug#43313)

Result sets with more than 250 fields could cause MySQL Proxy to crash. (Bug#43078)

MySQL Proxy would be unable to increase it's own maximum number of open files accorindg to the applied limit, if the limit was less than 8192. When set to debug level, MySQL Proxy will now report the open files limits and when the limits have been updated. (Bug#42783)

When connecting to a MySQL 4.0 server, the proxy would crash. You are now provided with an error message. (Bug#38601)

When using the rw-splitting.lua script you could get an error when talking to the backend server:

2008-07-28 18:00:30: (critical) (read_query) [string
"/usr/local/share/mysql-proxy/rw-splitting.l..."]:218: bad argument #1 to 'ipairs' (table
expected, got userdata)

This would lead to the proxy closing the connection to the configured MySQL backend. (Bug#38419)

When using MySQL Proxy with multiple backends, the failure of one backend would cause proxy to disconnect all backends and stop routing requests. (Bug#34793)