ProxySQL 1.4.5ProxySQL 1.4.5, released by ProxySQL, is now available for download in the Percona Repository along with an updated version of Percona’s proxysql-admin tool.

ProxySQL is a high-performance proxy, currently for MySQL and its forks (like Percona Server for MySQL and MariaDB). It acts as an intermediary for client requests seeking resources from the database. René Cannaò created ProxySQL for DBAs as a means of solving complex replication topology issues.

The ProxySQL 1.4.5 source and binary packages available at https://percona.com/downloads/proxysql include ProxySQL Admin – a tool, developed by Percona to configure Percona XtraDB Cluster nodes into ProxySQL. Docker images for release 1.4.5 are available as well: https://hub.docker.com/r/percona/proxysql/. You can download the original ProxySQL from https://github.com/sysown/proxysql/releases.

This release fixes the following bugs in ProxySQL Admin:

Usability improvements:

  • #PSQLADM-6: If the cluster node goes offline, the proxysql_node_monitor script now sets the node status as OFFLINE_HARD, and does not remove it from the ProxySQL database. Also, logging is consistent regardless of the cluster node online status.
  • #PSQLADM-30: Validation was added for the host priority file.
  • #PSQLADM-33: Added --proxysql-datadir option to run the proxysql-admin script with a custom ProxySQL data directory.
  • Also, BATS test suite was added for the proxysql-admin testing.

Bug fixes:

  • Fixed#PSQLADM-5: PXC mode specified with proxysql-admin with use of --mode parameter was not persistent.
  • Fixed#PSQLADM-8: ProxySQL High CPU load took place when mysqld was hanging.

ProxySQL is available under OpenSource license GPLv3.

2 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Ivan

In v1.4.5, I found that the percona & official proxysql file size is inconsistent
This has caused great trouble for us
Does the percona version of proxysql more worthy of our trust?

There was a big bug in the previous v1.4.3
For this issue, we reflected and resolved the solution with the official author.
Then we hesitate to wait for percona release v1.4.5
Or use the official v1.4.5
Finally we used the official v1.4.5 proxyql + percona v.1.4.3 admin tool

0
eppercona

Hi Ivan.
The binaries size differs because we strip them during package creation.
The following command is executed:
strip –remove-section=.comment –remove-section=.note proxysql

And this is why our binary is 4,5M instead of 22M

0