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

Change strict_multi_stmt default value

Browse Source 
The default value for strict_multi_stmt prevents compound statements and
atomic multi-statement commands from being executed without completely
disabling load balancing. As the new default value will have no practical
effect on all correct uses of readwritesplit, this is a relatively safe
thing to change.
This commit is contained in:
Markus Mäkelä
2017-12-20 23:50:07 +02:00
parent 9062c31865
commit d4aeca0d24
3 changed files with 29 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
Documentation/Release-Notes/MaxScale-2.2.1-Release-Notes.md
View File

@ -50,6 +50,21 @@ root@host:~# maxscale --user=root ...
The default value of the configuration parameter `detect_standalone_master` has
been changed from `false` to `true`.
### ReadWritesplit
The default value of `strict_multi_stmt` was changed to `false` to make
usage of atomic compound statements and multi-statement queries less
restrictive and to align it with the default value of `strict_sp_calls`.
Most cases where the functionality of `strict_multi_stmt` was triggered
were cases where the added safety of locking a session to the master did
more harm than it did good.
The only case where `strict_multi_stmt` should be enabled is when a
multi-statement or a compound statement modifies the state of the
session. This is not a good practice and a change in the client side
behavior is advised.
## Dropped Features
## New Features