From c015adfe9253981bc43c3d57202837d731e02da3 Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Thu, 21 Sep 2017 09:56:57 +0300 Subject: [PATCH] Update 2.1 release notes --- Documentation/Release-Notes/MaxScale-2.1.9-Release-Notes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/Release-Notes/MaxScale-2.1.9-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.1.9-Release-Notes.md index badf5c728..d3d9bdf85 100644 --- a/Documentation/Release-Notes/MaxScale-2.1.9-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.1.9-Release-Notes.md @@ -25,6 +25,7 @@ For any problems you encounter, please consider submitting a bug report at [Here is a list of bugs fixed in MaxScale 2.1.9.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.1.9) +* [MXS-1435](https://jira.mariadb.org/browse/MXS-1435) Persistent connections can hang on COM_QUIT * [MXS-1377](https://jira.mariadb.org/browse/MXS-1377) maxscale doesn't cleanup pid file on startup error * [MXS-1295](https://jira.mariadb.org/browse/MXS-1295) MaxScale's readwritesplit router does not take into account the fact that stored procedure call may change the value of a user variable