slave_run_triggers_for_rbr

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.

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

DETAILS

PARAMETERS

Dynamic

Yes

Scope

Global

Data Type

ENUM (NO, YES, LOGGING, ENFORCE)

Default Value

NO

SKYSQL

Cloud

SkySQL Topology

ES Ver

Default

AWS

HA (Primary/Replica)

10.4

NO

AWS

HA (Primary/Replica)

10.5

NO

AWS

Transactional Standalone

10.4

NO

AWS

Transactional Standalone

10.5

NO

AWS

Distributed Transactions

10.5

Not present

GCP

ColumnStore

10.5

NO

GCP

ColumnStore Multi

10.5

NO

GCP

Galera

10.4

NO

GCP

Galera

10.5

NO

GCP

HA (Primary/Replica)

10.4

NO

GCP

HA (Primary/Replica)

10.5

NO

GCP

HTAP

10.5

NO

GCP

Transactional Standalone

10.4

NO

GCP

Transactional Standalone

10.5

NO

GCP

Distributed Transactions

10.5

Not present

CHANGE HISTORY

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