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/performance-schema-status-variables.html
Performance Schema status variables have the following meanings: Performance_schema_accounts_lost The number of times a row could not be added to the accounts table because it was full. Performance_schema_digest_lost The number of digest instances ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-system-variable-tables.html
Note The value of the show_compatibility_56 system variable affects the information available from the tables described here. For details, see the description of that variable in Section 5.1.7, “Server System Variables”. The MySQL server ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-thread-filtering.html
The threads table contains a row for each server thread. Each row contains information about a thread and indicates whether monitoring is enabled for it. For the Performance Schema to monitor a thread, these things must be true: The ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-transaction-tables.html
Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store transaction events: events_transactions_current: The current transaction event for each ...
https://dev.mysql.com/doc/refman/5.7/en/point-in-time-recovery-binlog.html
This section explains the general idea of using the binary log to perform a point-in-time-recovery. The next section, Section 7.5.2, “Point-in-Time Recovery Using Event Positions”, explains the operation in details with an example. Note Many of ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-operation.html
Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL 8.0. This section describes how the query cache works when it is operational. Section 8.10.3.3, “Query Cache Configuration”, describes how to control whether it is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-pausing.html
You can stop and start replication on the replica using the STOP SLAVE and START SLAVE statements. The replication I/O thread continues to read events from the source but they are not executed. This makes it easier for the replica to catch up when ...
https://dev.mysql.com/doc/refman/5.7/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 SLAVE STATUS statement, which you must execute on each replica, ...
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 ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-functions.html
Certain functions do not replicate well under some conditions: The USER(), CURRENT_USER() (or CURRENT_USER), UUID(), VERSION(), and LOAD_FILE() functions are replicated without change and thus do not work reliably on the replica unless row-based ...