Replication Compatibility Between MySQL Versions This does not apply to the common sequence: Replication of session variables is not a problem when row-based replication is being used, in which case, session variables are always replicated safely. See Section 17.2.1, “Replication Formats” . The following session variables are written to the binary log and honored by the replica when parsing the binary log, regardless of the logging format: SET time_zone=...; INSERT INTO mytable VALUES(CONVERT_TZ(..., ..., @@time_zone)); • sql_mode • foreign_key_checks • unique_checks • character_set_client • collation_connection • collation_database • sql_auto_is_null • collation_server Important Even though session variables relating to character sets and collations are written to the binary log, replication between different character sets is not supported. To help reduce possible confusion, we recommend that you always use the same setting for the lower_case_table_names  system variable on both source and replica, especially when you are running MySQL on platforms with case-sensitive file systems. The  lower_case_table_names  setting can only be configured when initializing the server. Views are always replicated to replicas. 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 be filtered out by  replication-ignore-table  rules. Care should therefore be taken to ensure that views do not replicate table data that would normally be filtered for security reasons. Replication from a table to a same-named view is supported using statement-based logging, but not when using row-based logging. Trying to do so when row-based logging is in effect causes an error. 17.5.1.40 Replication and Views 17.5.2 Replication Compatibility Between MySQL Versions MySQL supports replication from one release series to the next higher release series. For example, you can replicate from a source running MySQL 5.6 to a replica running MySQL 5.7, from a source running MySQL 5.7 to a replica running MySQL 8.0, and so on. However, you might encounter difficulties when replicating from an older source to a newer replica if the source uses statements or relies on behavior no longer supported in the version of MySQL used on the replica. For example, foreign key names longer than 64 characters are no longer supported from MySQL 8.0. The use of more than two MySQL Server versions is not supported in replication setups involving multiple sources, regardless of the number of source or replica MySQL servers. This restriction applies not only to release series, but to version numbers within the same release series as well. For example, if you are 3681