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

Update readwritesplit limitations

Browse Source 
The use of multiple cursors was fixed in 2.2.5 and the multi-statement
LOAD DATA LOCAL INFILE is fixed in 2.3.0.
This commit is contained in:
Markus Mäkelä 2018-05-17 10:46:57 +03:00
parent bf933ecc22
commit 135cd2e16a
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 4 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/About/Limitations.md
View File

@ -179,15 +179,6 @@ Readwritesplit does not support pipelining of JDBC batched statements. This is
caused by the fact that readwritesplit executes the statements one at a time to
track the state of the response.
#### Prepared Statement Limitations
Readwritesplit does not support the parallel execution of binary protocol
prepared statements that use cursors. In practice this means that only one
open cursor is allowed when readwritesplit is used.
Opening more than one cursor will cause the execution of the prepared
statements to stall.
#### Limitations in multi-statement handling
When a multi-statement query is executed through the readwritesplit router, it
@ -195,6 +186,10 @@ will always be routed to the master. See
[`strict_multi_stmt`](../Routers/ReadWriteSplit.md#strict_multi_stmt) for more
details.
Execution of LOAD DATA LOCAL INFILE statements inside a multi-statement query is
not supported. If one is executed MaxScale will most likely hang (see
[MXS-1828](https://jira.mariadb.org/browse/MXS-1828)).
#### Limitations in client session handling
Some of the queries that a client sends are routed to all backends instead of