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/general-thread-states.html
Consequently, the thread is changing the temporary table from in-memory to disk-based format to save memory. The following list describes thread State values that are associated with general query processing and not more specialized activities such ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-install-windows-binary.html
To do this, create a new text file in Notepad or another text editor and enter the following text: [mysql_cluster] # Options for data node process: ndb-connectstring=198.51.100.10 # location of management server Save this file as C:\mysql\my.ini on ...You should also have the MySQL client (mysql.exe) on this ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-optimization.html
Certain types of queries for INFORMATION_SCHEMA tables can be optimized to execute more quickly. Note Comparison behavior for database and table names in INFORMATION_SCHEMA queries might differ from what you expect. 1) Try to use constant lookup ...
https://dev.mysql.com/doc/refman/5.7/en/limit-optimization.html
If you need only a specified number of rows from a result set, use a LIMIT clause in the query, rather than fetching the whole result set and throwing away the extra data. MySQL sometimes optimizes a query that has a LIMIT row_count clause and no ...
https://dev.mysql.com/doc/refman/5.7/en/mysqldumpslow.html
The MySQL slow query log contains information about queries that take a long time to execute (see Section 5.4.5, “The Slow Query Log”). Normally, mysqldumpslow groups queries that are similar except for the particular values of number and ...
https://dev.mysql.com/doc/refman/5.7/en/execution-plan-information.html
Depending on the details of your tables, columns, indexes, and the conditions in your WHERE clause, the MySQL optimizer considers many techniques to efficiently perform the lookups involved in an SQL query. A query on a huge table can be performed ...
https://dev.mysql.com/doc/refman/5.7/en/controlling-optimizer.html
MySQL provides optimizer control through system variables that affect how query plans are evaluated, switchable optimizations, optimizer and index hints, and the optimizer cost model.
https://dev.mysql.com/doc/refman/5.7/en/estimating-performance.html
In most cases, you can estimate query performance by counting disk seeks. For small tables, you can usually find a row in one disk seek (because the index is probably cached). For bigger tables, you can estimate that, using B-tree indexes, you need ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-optimizer.html
It is possible for the data on the source and replica to become different if a statement is written in such a way that the data modification is nondeterministic; that is, left up the query optimizer. (In general, this is not a good practice, even ...
https://dev.mysql.com/doc/refman/5.7/en/using-explain.html
See Section 8.2.2.1, “Optimizing Subqueries, Derived Tables, and View References with Semijoin Transformations”. The EXPLAIN statement provides information about how MySQL executes statements: EXPLAIN works with SELECT, DELETE, INSERT, REPLACE, ...