slave_run_triggers_for_rbr

This page is part of MariaDB's MariaDB Documentation.

Topics on this page:

Overview

In 10.6 ES, 10.6 CS, 10.5 ES, 10.5 CS, 10.4 ES:: Modes for how triggers in row-base replication on slave side will be executed. Legal values are NO (default), YES, LOGGING and ENFORCE. NO means that trigger for RBR will not be running on slave. YES and LOGGING means that triggers will be running on slave, if there was not triggers running on the master for the statement. LOGGING also means results of that the executed triggers work will be written to the binlog. ENFORCE means that triggers will always be run on the slave, even if there are triggers on the master. ENFORCE implies LOGGING.

In 10.6 ES, 10.5 ES, 10.4 ES:: Modes for how triggers in row-base replication on slave side will be executed. Legal values are NO (default), YES, LOGGING and ENFORCE. NO means that trigger for RBR will not be running on slave. YES and LOGGING means that triggers will be running on slave, if there was not triggers running on the master for the statement. LOGGING also means results of that the executed triggers work will be written to the binlog. ENFORCE means that triggers will always be run on the slave, even if there are triggers on the master. ENFORCE implies LOGGING.

In 10.4 CS, 10.3 ES, 10.3 CS, 10.2 ES, 10.2 CS:: Modes for how triggers in row-base replication on slave side will be executed. Legal values are NO (default), YES and LOGGING. NO means that trigger for RBR will not be running on slave. YES and LOGGING means that triggers will be running on slave, if there was not triggers running on the master for the statement. LOGGING also means results of that the executed triggers work will be written to the binlog.

Command-line	--slave_run_triggers_for_rbr={NO\|YES\|LOGGING\|ENFORCE}
Configuration file	Supported
Dynamic	Yes
Scope	Global
Data Type	ENUM (NO, YES, LOGGING, ENFORCE)
Default Value	NO

Cloud	SkySQL Topology	ES Ver	Default
AWS	Multi-Node Analytics	10.6	NO
	Single Node Analytics	10.6	NO
	Distributed Transactions	10.5	Not present
	Distributed Transactions	10.6	Not present
	Replicated Transactions	10.4	NO
		10.5	NO
		10.6	NO
	Single Node Transactions	10.4	NO
		10.5	NO
		10.6	NO
GCP	Multi-Node Analytics	10.6	NO
	Single Node Analytics	10.6	NO
	Distributed Transactions	10.5	Not present
	Distributed Transactions	10.6	Not present
	Replicated Transactions	10.4	NO
		10.5	NO
		10.6	NO
	Single Node Transactions	10.4	NO
		10.5	NO
		10.6	NO

Cloud	SkySQL Topology	ES Ver	Default
AWS	ColumnStore Data Warehouse	10.6	NO
	Xpand Distributed SQL	10.5	Not present
	Xpand Distributed SQL	10.6	Not present
	Enterprise Server With Replica(s)	10.4	NO
		10.5	NO
		10.6	NO
	Enterprise Server Single Node	10.4	NO
		10.5	NO
		10.6	NO
GCP	ColumnStore Data Warehouse	10.6	NO
	Xpand Distributed SQL	10.5	Not present
	Xpand Distributed SQL	10.6	Not present
	Enterprise Server With Replica(s)	10.4	NO
		10.5	NO
		10.6	NO
	Enterprise Server Single Node	10.4	NO
		10.5	NO
		10.6	NO

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.

Additional information on this topic may be found in the MariaDB Public Knowledge Base.