From 135cd2e16a10b698544aaccb327644aa5d02a558 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Thu, 17 May 2018 10:46:57 +0300 Subject: [PATCH] Update readwritesplit limitations 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. --- Documentation/About/Limitations.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/Documentation/About/Limitations.md b/Documentation/About/Limitations.md index c245c3be9..478664fb0 100644 --- a/Documentation/About/Limitations.md +++ b/Documentation/About/Limitations.md @@ -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