MySQL :: MySQL 9.7 Reference Manual

Search Results

Displaying 111 to 120 of 130 total results

https://dev.mysql.com/doc/refman/9.7/en/replication-features-triggers.html

If under row-based replication the replica applied the triggers as well as the row changes caused by them, the changes would in effect be applied twice on the replica, leading to different data on the source and the replica. With statement-based ...

19.5.1.40 Replication and Variables

https://dev.mysql.com/doc/refman/9.7/en/replication-features-variables.html

sql_mode is also replicated except for the NO_DIR_IN_CREATE mode; the replica always preserves its own value for NO_DIR_IN_CREATE, regardless of changes to it on the source. However, when mysqlbinlog parses a SET @@sql_mode = mode statement, the ...

19.1.3.3 GTID Auto-Positioning

https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-auto-positioning.html

The source and replica can diverge if any clients commit transactions on the source after it is restarted, which can lead to the situation where the source and replica are using the same GTID for different transactions. GTIDs replace the ...

19.1.6.5 Global Transaction ID System Variables

https://dev.mysql.com/doc/refman/9.7/en/replication-options-gtids.html

Leading and trailing blank spaces are accepted in the input value but omitted during tag creation. The MySQL Server system variables described in this section are used to monitor and control Global Transaction Identifiers (GTIDs). For additional ...

19.2.1.3 Determination of Safe and Unsafe Statements in Binary Logging

https://dev.mysql.com/doc/refman/9.7/en/replication-rbr-safe-unsafe.html

If a large number of such statements were executed on the source, this could lead to excessively large error log files. The “safeness” of a statement in MySQL replication refers to whether the statement and its effects can be replicated ...

19.2.5.4 Replication Channel Based Filters

https://dev.mysql.com/doc/refman/9.7/en/replication-rules-channel-based-filters.html

The following command options support channel specific replication filters using this format: --replicate-do-db=channel:database_id --replicate-ignore-db=channel:database_id --replicate-do-table=channel:table_id ... This section explains how to work ...

19.2.5.3 Interactions Between Replication Filtering Options

https://dev.mysql.com/doc/refman/9.7/en/replication-rules-examples.html

If you use a combination of database-level and table-level replication filtering options, the replica first accepts or ignores events using the database options, then it evaluates all events permitted by those options according to the table options. It is also important to note that the results vary depending on whether the operation is logged using statement-based or row-based binary logging ...

19.4 Replication Solutions

https://dev.mysql.com/doc/refman/9.7/en/replication-solutions.html

See Section 19.4.6, “Replicating Different Databases to Different Replicas” As the number of replicas increases, the load on the source can increase and lead to reduced performance (because of the need to replicate the binary log to each ...

15.6.7.4 RESIGNAL Statement

https://dev.mysql.com/doc/refman/9.7/en/resignal.html

RESIGNAL may change some or all information before passing it on. RESIGNAL is related to SIGNAL, but instead of originating a condition as SIGNAL does, RESIGNAL relays existing condition information, possibly after modifying it. RESIGNAL makes it ...

15.7.7.36 SHOW REPLICA STATUS Statement

https://dev.mysql.com/doc/refman/9.7/en/show-replica-status.html

Any changes, including NTP updates, can lead to clock skews that can make calculation of Seconds_Behind_Source less reliable. SHOW REPLICA STATUS [FOR CHANNEL channel] This statement provides status information on essential parameters of the ...

Displaying 111 to 120 of 130 total results