Search Results
https://dev.mysql.com/doc/refman/9.7/en/replication-features-load-data.html
If you need to recover from a replication error involving a LOAD DATA INFILE operation logged in statement format, and the replicated event is trusted, you could grant the FILE privilege to the PRIVILEGE_CHECKS_USER account temporarily, removing it ... LOAD DATA is considered unsafe for statement-based logging (see Section 19.2.1.3, “Determination of Safe and Unsafe Statements in Binary ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-max-allowed-packet.html
If you are replicating large column values (such as might be found in TEXT or BLOB columns) and max_allowed_packet is too small on the source, the source fails with an error, and the replica shuts down the replication I/O (receiver) thread.
https://dev.mysql.com/doc/refman/9.7/en/replication-features-partitioning.html
When the replica's copy of the table is partitioned but the source's copy is not, statements that act directly on partitions cannot be run on the source without causing errors there. Replication is supported between partitioned tables as long as ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-transactions.html
In MySQL 9.6 (and later), transactions that update both transactional tables and tables which are nontransactional or noncomposable are deprecated, and causes a deprecation warning to be written to both the client and the error log. In MySQL 9.6 ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-triggers.html
If an upgraded replication source server still has old replicas using MySQL versions that do not support multiple triggers, an error occurs on those replicas if a trigger is created on the source for a table that already has a trigger with the same ... With statement-based replication, triggers executed on the source also execute on the ...
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 ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-views.html
Trying to do so when row-based logging is in effect causes an error. Views are filtered by their own name, not by the tables they refer to. This means that a view can be replicated to the replica even if the view contains a table that would normally ...
https://dev.mysql.com/doc/refman/9.7/en/replication-functions-synchronization.html
The function returns NULL if the replication SQL thread is not started, the replica's source information is not initialized, the arguments are incorrect, or an error occurs. The functions listed in this section are used for controlling ...
https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-assign-anon.html
If the replica server is started without GTIDs enabled and with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS set for any replication channels, the settings are not changed, but a warning message is written to the error log explaining how to change the ...
https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-failover.html
When restoring a replica in a GTID based replication setup that has encountered an error, injecting an empty transaction may not solve the problem because an event does not have a GTID. There are a number of techniques when using MySQL Replication ...