diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-05-22 14:49:38 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-05-23 10:25:12 +0300 |
| commit | 1a6f470464171bd1144e4dd6f169bb4018f2e81a (patch) | |
| tree | 1e400c7e969dd07f4b60fdba504ff1c6545ff6bc /Docs | |
| parent | 47cede646b8f24b8dddc5bbb19b8e2b250858214 (diff) | |
| download | mariadb-git-1a6f470464171bd1144e4dd6f169bb4018f2e81a.tar.gz | |
MDEV-19544 Remove innodb_locks_unsafe_for_binlog
The transaction isolation levels READ COMMITTED and READ UNCOMMITTED
should behave similarly to the old deprecated setting
innodb_locks_unsafe_for_binlog=1, that is, avoid acquiring gap locks.
row_search_mvcc(): Reduce the scope of some variables, and clean up
the initialization and use of the variable set_also_gap_locks.
Diffstat (limited to 'Docs')
| -rw-r--r-- | Docs/README-wsrep | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/Docs/README-wsrep b/Docs/README-wsrep index 166901e111f..79278ed8927 100644 --- a/Docs/README-wsrep +++ b/Docs/README-wsrep @@ -269,9 +269,6 @@ innodb_autoinc_lock_mode=2 autoinc lock modes 0 and 1 can cause unresolved deadlock, and make the system unresponsive. -innodb_locks_unsafe_for_binlog=1 - This option is required for parallel applying. - 5.2 WSREP OPTIONS All options are optional except for wsrep_provider, wsrep_cluster_address, and |