PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-features-checksum-table.html
CHECKSUM TABLE returns a checksum that is calculated row by row, using a method that depends on the table row storage format. The storage format is not guaranteed to remain the same between MySQL versions, so the checksum value might change ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-directory.html
If a DATA DIRECTORY or INDEX DIRECTORY table option is used in a CREATE TABLE statement on the source server, the table option is also used on the replica. This can cause problems if no corresponding directory exists in the replica host's file ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-load-data.html
LOAD DATA is considered unsafe for statement-based logging (see Section 16.2.1.3, “Determination of Safe and Unsafe Statements in Binary Logging”). When binlog_format=MIXED is set, the statement is logged in row-based format. When ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-optimizer.html
It is possible for the data on the source and replica to become different if a statement is written in such a way that the data modification is nondeterministic; that is, left up the query optimizer. (In general, this is not a good practice, even ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-partitioning.html
Replication is supported between partitioned tables as long as they use the same partitioning scheme and otherwise have the same structure except where an exception is specifically allowed (see Section 16.4.1.10, “Replication with Differing Table ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-repair-table.html
When used on a corrupted or otherwise damaged table, it is possible for the REPAIR TABLE statement to delete rows that cannot be recovered. However, any such modifications of table data performed by this statement are not replicated, which can ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-shutdowns.html
It is safe to shut down a source server and restart it later. When a replica loses its connection to the source, the replica tries to reconnect immediately and retries periodically if that fails. A replica also is able to deal with network ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-timezone.html
By default, source and replica servers assume that they are in the same time zone. If you are replicating between servers in different time zones, the time zone must be set on both source and replica. Otherwise, statements depending on the local ...
https://dev.mysql.com/doc/refman/5.7/en/replication-implementation.html
Replication is based on the replication source server keeping track of all changes to its databases (updates, deletes, and so on) in its binary log. The binary log serves as a written record of all events that modify database structure or content ...
https://dev.mysql.com/doc/refman/5.7/en/replication-mode-change-online-enable-gtids.html
This section describes how to enable GTID transactions, and optionally auto-positioning, on servers that are already online and using anonymous transactions. This procedure does not require taking the server offline and is suited to use in ...