[MDEV-19544] Remove innodb_locks_unsafe_for_binlog Created: 2019-05-22  Updated: 2021-03-22  Resolved: 2019-05-23

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.5.0

Type: Task Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MDEV-24224 Gap lock on delete in 10.5 using READ... Closed
Relates
relates to MDEV-19563 Galera depends on deprecated option i... Closed
relates to MDEV-21822 InnoDB: Failing assertion: UT_LIST_GE... Closed
relates to MDEV-18650 Options deprecated in previous versions Closed
relates to MDEV-20605 Awaken transaction can miss inserted ... Closed

 Description   

The parameter innodb_locks_unsafe_for_binlog was deprecated in MariaDB 10.0. Let us finally remove it.

 Comments   
Comment by Marko Mäkelä [ 2019-05-22 ]

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?

Generated at Thu Feb 08 08:52:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.