Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
The parameter innodb_locks_unsafe_for_binlog was deprecated in MariaDB 10.0. Let us finally remove it.
Attachments
Issue Links
- causes
-
MDEV-24224 Gap lock on delete in 10.5 using READ COMMITTED
-
- Closed
-
- relates to
-
MDEV-19563 Galera depends on deprecated option innodb_locks_unsafe_for_binlog
-
- Closed
-
-
MDEV-21822 InnoDB: Failing assertion: UT_LIST_GET_LEN(trx->lock.trx_locks) == 0 upon trivial SELECT from InnoDB table after wrong operations with sequences
-
- Closed
-
-
MDEV-18650 Options deprecated in previous versions
-
- Closed
-
-
MDEV-20605 Awaken transaction can miss inserted by other transaction records due to wrong persistent cursor restoration
-
- Closed
-
Galera’s plugin/wsrep_info/mysql-test/wsrep_info/my.cnf was setting innodb_locks_unsafe_for_binlog=1. I believe that it should set tx_isolation=READ-COMMITTED instead, or perhaps, even better, we should have some WSREP tweak in InnoDB source code. seppo, can you please think of a fix?