Functionality added or changed:
Bugs fixed:
A memory leak occurred in MySQL Proxy if clients older than MySQL 4.1 connected to it. (Bug#50993)
A segmentation fault occurred in MySQL Proxy if clients older than MySQL 4.1 connected to it. (Bug#48641)
MySQL Proxy would load a configuration file with unsafe permissions, which could permit password information to be exposed through the file. MySQL Proxy now refuses to load a configuration file with unsafe permissions. (Bug#47589)
Several supplied scripts were updated to account for flag and structure changes:
active-transactions.lua
was updated to use theresultset_is_needed
flag.ro-balance.lua
was updated to use theresultset_is_needed
flag and updatedproxy.connection.dst.name
structure.rw-splitting.lua
was updated to use theresultset_is_needed
flag and updatedproxy.connections
structure.
(Bug#47349, Bug#45408, Bug#47345, Bug#43424, Bug#42841, Bug#46141)
The line numbers provided in stack traces were off by one. (Bug#47348)
MySQL Proxy accepted more than one address in the value of the
--proxy-backend-addresses
option. You should specify one--proxy-backend-addresses
option for each backend address. (Bug#47273)MySQL Proxy returned the wrong version string internally from the
proxy.PROXY_VERSION
constant. (Bug#45996)MySQL Proxy could stop accepting network packets if it received a large number of packets. The listen queue has been extended to permit a larger backlog. (Bug#45878, Bug#43278)
Due to a memory leak, memory usage for each new connection to the proxy increased, leading to very high consumption. (Bug#45272)
MySQL Proxy failed to work with certain versions of MySQL, including MySQL 5.1.15, where a change in the MySQL protocol existed. Now Proxy denies
COM_CHANGE_USER
commands when it is connected to MySQL 5.1.14 to 5.1.17 servers by sending back an error:COM_CHANGE_USER is broken on 5.1.14-.17, please upgrade the MySQL Server
. (Bug#45167)See also Bug#25371.
Logging to
syslog
with the--log-use-syslog
option did not work. (Bug#36431)MySQL Proxy could incorrectly insert
NULL
values into the returned result set, even though non-NULL
values were returned in the original query. (Bug#35729)MySQL Proxy raised an error when processing query packets larger than 16MB. (Bug#35202)