Replication Notes And Tips; Replication Features And Issues - Oracle 5.0 Reference Manual

You can use the
successfully.
For more information on the
Syntax".
TO
If you want to enforce the use of SSL connections during replication, then create a user with the
REPLICATION SLAVE
mysql> CREATE USER 'repl'@'%.mydomain.com' IDENTIFIED BY 'slavepass';
mysql> GRANT REPLICATION SLAVE ON *.*
-> TO 'repl'@'%.mydomain.com' REQUIRE SSL;
If the account already exists, you can add
mysql> GRANT USAGE ON *.*
-> TO 'repl'@'%.mydomain.com' REQUIRE SSL;

16.4. Replication Notes and Tips

16.4.1. Replication Features and Issues

The following sections provide information about what is supported and what is not in MySQL
replication, and about specific issues and situations that may occur when replicating certain
statements.
Statement-based replication depends on compatibility at the SQL level between the master and slave.
In others, successful SBR requires that any SQL features used be supported by both the master and
the slave servers. For example, if you use a feature on the master server that is available only in
MySQL 5.0 (or later), you cannot replicate to a slave that uses MySQL 4.1 (or earlier).
Such incompatibilities also can occur within a release series when using pre-production releases of
MySQL. For example, the
this function on the master, you cannot replicate to a slave that uses MySQL 5.0.11 or earlier.
For this reason, use Generally Available (GA) releases of MySQL for statement-based replication in a
production setting, since we do not introduce new SQL statements or change their behavior within a
given release series once that series reaches GA release status.
If you are planning to use replication between MySQL 5.0 and a previous MySQL release series, it is
also a good idea to consult the edition of the MySQL Reference Manual corresponding to the earlier
release series for information regarding the replication characteristics of that series.
For additional information specific to replication and InnoDB, see
MySQL Replication".
16.4.1.1. Replication and
Replication of AUTO_INCREMENT,
correctly, subject to the following exceptions.
•
AUTO_INCREMENT
is,
AUTO_INCREMENT
This is a known issue which is fixed in MySQL 5.5. (Bug #12669186)
•
INSERT DELAYED ... VALUES(LAST_INSERT_ID())
and the slave. (Bug #20819) This is fixed in MySQL 5.1 when using row-based or mixed-format
binary logging. For more information, see
• Before MySQL 5.0.26, a stored procedure that uses
properly.
Replication Notes and Tips
SHOW SLAVE STATUS
CHANGE MASTER TO
[577] privilege and use the
[967]
SLEEP()
AUTO_INCREMENT
LAST_INSERT_ID()
columns in tables on the slave must match the same columns on the master; that
columns must be replicated to
statement to confirm that the SSL connection was established
statement, see
REQUIRE SSL
to it with this statement:
REQUIRE SSL
function is available beginning with MySQL 5.0.12. If you use
[961], and
AUTO_INCREMENT
inserts a different value on the master
Replication Formats.
LAST_INSERT_ID()
1497
Section 13.4.2.1, "CHANGE MASTER
option for that user. For example:
Section 14.2.3.5, "InnoDB
values is done
TIMESTAMP
columns.
[961] does not replicate
and