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

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

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

MySQL Proxy was unable to increase its own maximum number of open files according to the limit specified by the --max-open-files option, if the limit was less than 8192. When set to debug level, Proxy now reports the open files limit and when the limit has been updated. (Bug#42783)

MySQL Proxy crashed when connecting to a MySQL 4.0 server. Now it generates an error message instead. (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 led to Proxy closing the connection to the configured MySQL backend. (Bug#38419)

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