mariadb/mysql-test/suite/galera_3nodes_sr
Marko Mäkelä 4e1e9ea6f3 MDEV-35124 Set innodb_snapshot_isolation=ON by default
From the very beginning, the default InnoDB transaction isolation level
REPEATABLE READ does not correspond to any well formed definition.
The main issue is the lack of write/write conflict detection.
To fix that and to make REPEATABLE READ correspond to Snapshot Isolation,
b8a6719889 introduced the Boolean
session variable innodb_snapshot_isolation. It was 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.
2024-10-11 15:02:31 +03:00
..
r MDEV-35124 Set innodb_snapshot_isolation=ON by default 2024-10-11 15:02:31 +03:00
t MDEV-35124 Set innodb_snapshot_isolation=ON by default 2024-10-11 15:02:31 +03:00
disabled.def MDEV-29892 : Galera test failure on galera_sr_kill_slave_after_apply_rollback2 2023-12-21 10:46:17 +01:00
galera_3nodes.cnf Galera4 2019-01-23 15:30:00 +04:00
my.cnf Galera4 2019-01-23 15:30:00 +04:00
suite.pm MDEV-26707 SR transaction rolls back locally, but not in cluster 2021-10-12 07:25:13 +03:00