PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/repair-table.html
[QUICK] [EXTENDED] [USE_FRM] REPAIR TABLE repairs a possibly corrupted table, for certain storage engines only. Although normally you should never have to run REPAIR TABLE, if disaster strikes, this statement is very likely to get back all your data ...
https://dev.mysql.com/doc/refman/8.0/en/replace.html
REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] { {VALUES | VALUE} (value_list) [, (value_list)] ... | VALUES row_constructor_list } REPLACE [LOW_PRIORITY | DELAYED] ...
https://dev.mysql.com/doc/refman/8.0/en/replication-administration-status.html
The most common task when managing a replication process is to ensure that replication is taking place and that there have been no errors between the replica and the source. The SHOW REPLICA STATUS statement, which you must execute on each replica, ...
https://dev.mysql.com/doc/refman/8.0/en/replication-asynchronous-connection-failover-source.html
To activate asynchronous connection failover for a replication channel set SOURCE_CONNECTION_AUTO_FAILOVER=1 on the CHANGE REPLICATION SOURCE TO statement (from MySQL 8.0.23) or CHANGE MASTER TO statement (before MySQL 8.0.23) for the channel. GTID ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
https://dev.mysql.com/doc/refman/8.0/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 ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-gtids.html
The MySQL Server system variables described in this section are used to monitor and control Global Transaction Identifiers (GTIDs). For additional information, see Section 19.1.3, “Replication with Global Transaction Identifiers”.
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-channel-based-filters.html
This section explains how to work with replication filters when multiple replication channels exist, for example in a multi-source replication topology. Before MySQL 8.0, all replication filters were global, so filters were applied to all ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-interface.html
When you install the source and replica plugins for semisynchronous replication (see Section 19.4.10.1, “Installing Semisynchronous Replication”), system variables become available to control plugin behavior. To check the current values of the ...
https://dev.mysql.com/doc/refman/8.0/en/reproducible-test-case.html
For information about steps to take when encountering InnoDB table corruption, see Section 1.5, “How to Report Bugs or Problems”. If you encounter corrupted MyISAM tables or if mysqld always fails after some update statements, you can test ...