binlog_direct_non_transactional_updates

Overview

Causes updates to non-transactional engines using statement format to be written directly to binary log. Before using this option make sure that there are no dependencies between transactional and non-transactional tables such as in the statement INSERT INTO t_myisam SELECT * FROM t_innodb; otherwise, slaves may diverge from the master.

DETAILS

PARAMETERS

Command-line

--binlog_direct_non_transactional_updates[={OFF|ON}]

Configuration file

Supported

Dynamic

Yes

Scope

Global, Session

Data Type

BOOLEAN (OFF, ON)

Default Value

OFF

SKYSQL

Cloud

SkySQL Topology

ES Ver

Default

AWS

Multi-Node Analytics

10.6

OFF

Single Node Analytics

10.6

OFF

Distributed Transactions

10.5

Not present

10.6

Not present

Replicated Transactions

10.4

OFF

10.5

OFF

10.6

OFF

Single Node Transactions

10.4

OFF

10.5

OFF

10.6

OFF

GCP

Multi-Node Analytics

10.6

OFF

Single Node Analytics

10.6

OFF

Distributed Transactions

10.5

Not present

10.6

Not present

Replicated Transactions

10.4

OFF

10.5

OFF

10.6

OFF

Single Node Transactions

10.4

OFF

10.5

OFF

10.6

OFF

Cloud

SkySQL Topology

ES Ver

Default

AWS

ColumnStore Data Warehouse

10.6

OFF

Xpand Distributed SQL

10.5

Not present

10.6

Not present

Enterprise Server With Replica(s)

10.4

OFF

10.5

OFF

10.6

OFF

Enterprise Server Single Node

10.4

OFF

10.5

OFF

10.6

OFF

GCP

ColumnStore Data Warehouse

10.6

OFF

Xpand Distributed SQL

10.5

Not present

10.6

Not present

Enterprise Server With Replica(s)

10.4

OFF

10.5

OFF

10.6

OFF

Enterprise Server Single Node

10.4

OFF

10.5

OFF

10.6

OFF

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Present starting 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.

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

EXTERNAL REFERENCES