Details
-
Task
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
Description
From the very beginning, the default InnoDB transaction isolation level REPEATABLE READ does not correspond to any established definition. The main issue is the lack of write/write conflict detection. To fix that and to make REPEATABLE READ correspond to Snapshot Isolation, we introduced the Boolean session variable innodb_snapshot_isolation in MariaDB Server 10.6.18, 10.11.8, 11.4.2. It is disabled by default in order not to break any user applications.
In a new major version of MariaDB Server, we had better enable this parameter by default, so that bugs like MDEV-26642, MDEV-26643, MDEV-32898 will be avoided by default.
Attachments
Issue Links
- causes
-
MDEV-35488 innodb_snapshot_isolation is ON by default in 11.6+
- Closed
- relates to
-
MDEV-26642 Weird SELECT view when a record is modified to the same value by two transactions
- Closed
-
MDEV-26643 Inconsistent behaviors of UPDATE under RU & RC isolation level
- Closed
-
MDEV-32898 Phantom rows caused by UPDATE of PRIMARY KEY
- Closed
-
MDEV-35140 Support innodb-snapshot-isolation in Galera cluster
- In Progress