Oracle 5.0, Справочное руководство

Страница: 1528 / 3232

Replication Compatibility Between MySQL Versions
1508
SET max_join_size=1000;
INSERT INTO mytable VALUES(@@max_join_size);
This does not apply to the common sequence, which replicates correctly as of MySQL 5.0.4.
SET time_zone=...;
INSERT INTO mytable VALUES(CONVERT_TZ(..., ..., @@time_zone));
Update statements that refer to user-defined variables (that is, variables of the form
@var_name
) are
replicated correctly in MySQL 5.0. However, this is not true for versions prior to 4.1. Note that user
variable names are case insensitive starting in MySQL 5.0. You should take this into account when
setting up replication between MySQL 5.0 and older versions.
In MySQL 5.0.46 and later, the following session variables are written to the binary log and honored by
the replication slave when parsing the binary log, regardless of the logging format:
•
sql_mode
[495]
•
foreign_key_checks
[451]
•
unique_checks
[504]
•
character_set_client
[441]
•
collation_connection
[443]
•
collation_database
[444]
•
collation_server
[444]
•
sql_auto_is_null
[493]
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.
It is strongly recommended that you always use the same setting for the
lower_case_table_names
[466] system variable on both master and slave. In particular, when a
case-sensitive file system is used, and this variable set to 1 on the slave, but to a different value on the
master, names of databases are not converted to lowercase, which can cause replication to fail. This is
a known issue, which is fixed in MySQL 5.6.
16.4.2. Replication Compatibility Between MySQL Versions
MySQL supports replication from one major version to the next higher major version. For example, you
can replicate from a master running MySQL 4.1 to a slave running MySQL 5.0, from a master running
MySQL 5.0 to a slave running MySQL 5.1, and so on.
However, one may encounter difficulties when replicating from an older master to a newer slave if the
master uses statements or relies on behavior no longer supported in the version of MySQL used on the
slave.
The use of more than 2 MySQL Server versions is not supported in replication setups involving multiple
masters, regardless of the number of master or slave MySQL servers. This restriction applies not only
to major versions, but to minor versions within the same major version as well. For example, if you
are using a chained or circular replication setup, you cannot use MySQL 5.0.21, MySQL 5.0.22, and
MySQL 5.0.24 concurrently, although you could use any 2 of these releases together.
In some cases, it is also possible to replicate between a master and a slave that is more than one
major version newer than the master. However, there are known issues with trying to replicate from