PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replica-logs.html
Updates to the replica's applier metadata repository table are committed together with the transactions, meaning that the replica's progress information recorded in that repository is always consistent with what has been applied to the database, ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-differing-tables.html
In all cases where the source and target tables do not have identical definitions, the database and table names must be the same on both the source and the replica. Source and target tables for replication do not have to be identical. A table on ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-directory.html
The result is that MyISAM data and index files are created in the table's database directory. 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 system or if it exists but is not accessible to the replica ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-errors.html
If a statement produces different errors on the source and the replica, the replication SQL thread terminates, and the replica writes a message to its error log and waits for the database administrator to decide what to do about the error. If a ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-flush.html
If you replicate the privilege tables in the mysql database and update those tables directly without using GRANT, you must issue a FLUSH PRIVILEGES on the replicas to put the new privileges into effect. Some forms of the FLUSH statement are not ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-transaction-inconsistencies.html
If a replication channel has gaps, it has the following consequences: The replica database is in a state that may never have existed on the source. Inconsistencies in the sequence of transactions that have been executed from the relay log can occur ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-failover.html
GTIDs play a key role in applying changes to the database: the server automatically skips any transaction having an identifier which the server recognizes as one that it has processed before. There are a number of techniques when using MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-configuration.html
The replica replicates one database from each of the sources, db1 from source1 and db2 from source2. A multi-source replication topology requires at least two sources and one replica configured. In these tutorials, we assume you have two sources ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-backups-rawdata.html
If the MySQL server is still running, background tasks may still be updating the database files, particularly those involving storage engines with background processes such as InnoDB. To guarantee the integrity of the files that are copied, backing ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-backups-read-only.html
Note The instructions in this section place the server to be backed up in a state that is safe for backup methods that get the data from the server, such as mysqldump (see Section 4.5.4, “mysqldump — A Database Backup Program”). You should not ...