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/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 9.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/8.0/en/point-in-time-recovery-positions.html
The last section, Section 9.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 20:06:00 on March 11, 2020, an SQL statement ...
https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html
The SELECT privilege is needed for tables or views used with EXPLAIN, including any underlying tables in view definitions. The privileges granted to a MySQL account determine which operations the account can perform. MySQL privileges differ in the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-key-rotation.html
If any of the first four steps of the binary log master key rotation process cannot be completed correctly, an error message is issued explaining the situation and the consequences for the encryption status of the binary log files and relay log ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html
This section explains the server options and system variables that apply to replica servers and contains the following: Startup Options for Replica Servers System Variables Used on Replica Servers Specify the options either on the command line or ...Many of the options can be set while the server is running by using the CHANGE REPLICATION SOURCE TO statement (from MySQL 8.0.23) or CHANGE MASTER TO statement (before MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/row-constructor-optimization.html
However, the row constructor itself does not cover an index prefix, with the result that the optimizer uses only c1 (key_len=4, the size of c1): mysql> EXPLAIN SELECT * FROM t1 WHERE c1=1 AND (c2,c3) > (1,1)\G *************************** 1. For ...
https://dev.mysql.com/doc/refman/8.0/en/select.html
These tables appear first in the query plan displayed by EXPLAIN. SELECT [ALL | DISTINCT | DISTINCTROW ] [HIGH_PRIORITY] [STRAIGHT_JOIN] [SQL_SMALL_RESULT] [SQL_BIG_RESULT] [SQL_BUFFER_RESULT] [SQL_NO_CACHE] [SQL_CALC_FOUND_ROWS] select_expr [, ...
https://dev.mysql.com/doc/refman/8.0/en/subquery-materialization.html
Use of EXPLAIN with a query provides some indication of whether the optimizer uses subquery materialization: Compared to query execution that does not use materialization, select_type may change from DEPENDENT SUBQUERY to SUBQUERY. For extended ...
https://dev.mysql.com/doc/refman/8.0/en/sys-ps-trace-statement-digest.html
The procedure also attempts to execute EXPLAIN for the longest running example of the digest during the interval. Traces all Performance Schema instrumentation for a specific statement digest. If you find a statement of interest within the ...
https://dev.mysql.com/doc/refman/8.0/en/using-log-files.html
You can also try the command EXPLAIN on all SELECT statements that takes a long time to ensure that mysqld is using indexes properly. Note that before starting mysqld with the general query log enabled, you should check all your tables with ...