slave_run_triggers_for_rbr

In 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.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.

See also: System Variables 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

--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

SkySQL Default (Standalone 10.4)

NO

SkySQL Default (Standalone 10.5)

NO

SkySQL Default (Primary/Replica 10.4)

NO

SkySQL Default (Primary/Replica 10.5)

NO

SkySQL Default (Analytical 10.4)

NO

SkySQL Default (HTAP 10.4)

NO

SkySQL Default (Xpand 10.5)

NO

See MariaDB SkySQL documentation to learn more about the MariaDB SkySQL database as a service.

CHANGE HISTORY

Release Series

History

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.

EXTERNAL REFERENCES