So, I admit the title for this post is a bit ambiguous. Not only
is it the second post I’ve written in a short period of time, but
it’s also focused on ProxySQL 2.0. As promised in the previous post, I’ve upgraded my testing
environment to ProxySQL 2.0 and was interested to see if there
are any differences in behaviour from the previous version. As it
turns out, there are.
In the comments section of the previous post, you’ll find a
comment by ProxySQL Founder and CEO, René Cannaò:
“Indeed ProxySQL doesn’t support caching_sha2_password
authentication plugin, but since ProxySQL 2.0.3 (March 2019) a
client connection using caching_sha2_password will be
automatically switched to mysql_native_password.
With regards to “OPT_CHARSET_NAME=utf8”, the problem is that
your backend it is not MySQL 8.0 …[Read more]