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/mysqlcheck.html
--write-binlog Command-Line Format --write-binlog This option is enabled by default, so that ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE statements generated by mysqlcheck are written to the binary log. The mysqlcheck client performs table ...
https://dev.mysql.com/doc/refman/5.7/en/optimizer-hints.html
If DUPSWEEDOUT is disabled, on occasion the optimizer may generate a query plan that is far from optimal. One means of control over optimizer strategies is to set the optimizer_switch system variable (see Section 8.9.2, “Switchable ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-selection.html
MySQL 5.7 supports explicit selection of partitions and subpartitions that, when executing a statement, should be checked for rows matching a given WHERE condition. Partition selection is similar to partition pruning, in that only specific ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-status-monitoring.html
All the historical data generated by the plugin code is still available, but new events for the instruments are not collected. Names for these variables have several forms: Performance_schema_xxx_classes_lost indicates how many instruments of type ...
https://dev.mysql.com/doc/refman/5.7/en/point-in-time-recovery-binlog.html
The source of information for point-in-time recovery is the set of binary log files generated subsequent to the full backup operation. This section explains the general idea of using the binary log to perform a point-in-time-recovery. The next ...
https://dev.mysql.com/doc/refman/5.7/en/point-in-time-recovery-positions.html
The last section, Section 7.5.1, “Point-in-Time Recovery Using Binary Log”, explains the general idea of using the binary log to perform a point-in-time-recovery. As an example, suppose that around 13:00:00 on May 27, 2020, an SQL statement was ...
https://dev.mysql.com/doc/refman/5.7/en/query-log.html
Server restarts and log flushing do not cause a new general query log file to be generated (although flushing closes and reopens it). The general query log is a general record of what mysqld is doing. The server writes information to this log when ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-skip.html
If the failing transaction generated an error in a worker thread, you can obtain its GTID directly from the APPLYING_TRANSACTION field in the Performance Schema table replication_applier_status_by_worker. If replication stops due to an issue with ...
https://dev.mysql.com/doc/refman/5.7/en/replication-channels.html
The error codes and messages that are issued when multi-source replication is enabled specify the channel that generated the error. In MySQL multi-source replication, a replica opens multiple replication channels, one for each replication source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-delayed.html
MySQL 5.7 supports delayed replication such that a replica server deliberately lags behind the source by at least a specified amount of time. Use the MASTER_DELAY option for CHANGE MASTER TO to set the delay to N seconds: CHANGE MASTER TO ...