hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add changes to persistent connections to documentation

Browse Source 
The documentation now states that, starting with 2.1, the persistent
connections will reset the MySQL session state when they are taken into
use.
This commit is contained in:
Markus Makela
2016-11-01 11:20:34 +02:00
parent 57eb599769
commit d69025bfa6
2 changed files with 28 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/Release-Notes/MaxScale-2.1.0-Release-Notes.md
View File

@ -57,6 +57,18 @@ by default, is configured using the new global configuration entry `log_throttli
For more information about this configuration entry, please see
[Global Settings](../Getting-Started/Configuration-Guide.md#global-settings).
### Persistent Connections
Starting with the 2.1 version of MariaDB MaxScale, when a MySQL protocol
persistent connection is taken from the persistent connection pool, the
state of the MySQL session will be reset when the the connection is used
for the first time. This allows persistent connections to be used with no
functional limitations and makes them behave like normal MySQL
connections.
For more information about persistent connections, please read the
[Administration Tutorial](../Tutorials/Administration-Tutorial.md).
### User data cache
The user data cache stores the cached credentials that are used by some router