PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replica-logs.html
A replica server creates several repositories of information to use for the replication process: The relay log, which is written by the replication I/O thread, contains the transactions read from the replication source server's binary log. The ...
https://dev.mysql.com/doc/refman/5.7/en/replica-sql-thread-states.html
Making temporary file (create) before replaying LOAD DATA INFILE The thread is executing a LOAD DATA statement and is creating a temporary file containing the data from which the replica reads rows. This state can only be encountered if the original ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-auto-increment.html
Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID(), and TIMESTAMP values is done correctly, subject to the following exceptions: When using statement-based replication prior to MySQL 5.7.1, AUTO_INCREMENT columns in tables on the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-create-select.html
SELECT statement to make any changes in tables other than the table that is created by the statement. Some older versions of MySQL permitted these statements to do so; this means that, when using replication between a MySQL 5.6 or later replica and ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-limit.html
Statement-based replication of LIMIT clauses in DELETE, UPDATE, and INSERT ... SELECT statements is unsafe since the order of the rows affected is not defined. (Such statements can be replicated correctly with statement-based replication only if ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-max-allowed-packet.html
max_allowed_packet sets an upper limit on the size of any single message between the MySQL server and clients, including replicas. If you are replicating large column values (such as might be found in TEXT or BLOB columns) and max_allowed_packet is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-transactions.html
In general, you should avoid transactions that update both transactional and nontransactional tables in a replication environment. You should also avoid using any statement that accesses both transactional (or temporary) and nontransactional tables ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-triggers.html
With statement-based replication, triggers executed on the source also execute on the replica. With row-based replication, triggers executed on the source do not execute on the replica. Instead, the row changes on the source resulting from trigger ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features.html
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 ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
Because GTID-based replication is dependent on transactions, some features otherwise available in MySQL are not supported when using it. This section provides information about restrictions on and limitations of replication with GTIDs. When using ...