On 4/2/24 15:00, Marc wrote:
I think the initial post with error message is clear
" blocked because of many connections"
so it was "too many connections" after all, not "too many connection
errors"?
in that case you had us all lead on the wrong track, and the solution
would be simple: increase max_connections
But my intial question was also if the blocking could be expanded to a match of
ip+db and not just ip. I still think this could be an interesting change in
design.
that again hints towards "too many connection errors"
All this mess could have been avoided by a clear copy+paste of the error
message you are actually getting, instead of trying to be as vague as
possible (e.g. not mentioning actual old and new version, even after
repeated questions about that).
So back to "too many connection errors": as described in my last reply
this error is about misbehaved clients that have repeatedly connected
to the server, but then aborted before completing the login handshake.
And with that the IP is the only thing known at that point, user name
and the optional up-front default database are only transferred later
in the handshake.
So it is an interesting feature request, but one impossible to add to
that specific feature.
PS: so you tricked me into replying once more, while again not really
adding any useful information. Won't happen again though ...
--
Hartmut Holzgraefe, Principal Support Engineer (EMEA)
MariaDB Corporation | http://www.mariadb.com/
_______________________________________________
discuss mailing list -- [email protected]
To unsubscribe send an email to [email protected]
