innodb_locks_unsafe_for_binlog

Overview

In 10.6 ES, 10.6 CS, 10.5 ES, 10.5 CS:

Not present

In 10.4 ES, 10.4 CS, 10.3 ES, 10.3 CS, 10.2 ES, 10.2 CS:

DEPRECATED. This option may be removed in future releases. Please use READ COMMITTED transaction isolation level instead. Force InnoDB to not use next-key locking, to use only row-level locking.

See also: System Variables for MariaDB Enterprise Server 10.6, in 10.6 CS, in 10.5 ES, in 10.5 CS, in 10.4 ES, in 10.4 CS, in 10.3 ES, in 10.3 CS, in 10.2 ES, and in 10.2 CS

DETAILS

PARAMETERS

Command-line

--innodb_locks_unsafe_for_binlog

Configuration file

Supported

Dynamic

No

Scope

Global

Data Type

BOOLEAN (OFF, ON)

Default Value

OFF

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Not present.

10.6 Community

  • Not present.

10.5 Enterprise

  • Removed in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Removed in MariaDB Community Server 10.5.0.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0.

EXTERNAL REFERENCES