slave_run_triggers_for_rbr
This page is part of MariaDB's Documentation.
The parent of this page is: System Variables for MariaDB Enterprise Server
Topics on this page:
Overview
In 23.08 ES, 23.07 ES, 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 23.08 ES, 23.07 ES, 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.
USAGE
DETAILS
SYNONYMS
SCHEMA
PARAMETERS
Command-line | --slave_run_triggers_for_rbr={NO| |
Configuration file | Supported |
Dynamic | Yes |
Scope | Global |
Data Type | ENUM (NO, YES, LOGGING, ENFORCE) |
Product Default Value | NO |
SKYSQL
Cloud | SkySQL Topology | ES Ver | Service Default |
---|---|---|---|
AWS | Multi-Node Analytics | 10.6 | NO |
Single Node Analytics | 10.6 | NO | |
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 | |
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 | Service Default |
---|---|---|---|
AWS | ColumnStore Data Warehouse | 10.6 | NO |
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 |
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 |
See SkySQL details in MariaDB SkySQL previous release
See SkySQL details in MariaDB SkySQL new release
PRIVILEGES
EXAMPLES
ERROR HANDLING
FEATURE INTERACTION
RESPONSES
DIAGNOSIS
ISO 9075:2016
CHANGE HISTORY
Release Series | History |
---|---|
23.08 Enterprise |
|
23.07 Enterprise |
|
10.6 Enterprise |
|
10.6 Community |
|
10.5 Enterprise |
|
10.5 Community |
|
10.4 Enterprise |
|
10.4 Community |
|
10.3 Enterprise |
|
10.3 Community |
|
10.2 Enterprise |
|
10.2 Community |
|
Release Series | History |
---|---|
23.08 Enterprise |
|
23.07 Enterprise |
|
10.6 Enterprise |
|
10.5 Enterprise |
|
10.4 Enterprise |
|
RELATED TOPICS
EXTERNAL REFERENCES
Additional information on this topic may be found in the MariaDB Public Knowledge Base.