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/switchable-optimizations.html
The following list describes the permissible opt_name flag names, grouped by optimization strategy: Batched Key Access Flags batched_key_access (default off) Controls use of BKA join algorithm. For more information, see Section 8.2.1.11, “Block ...
https://dev.mysql.com/doc/refman/5.7/en/converting-tables-to-innodb.html
Because lookups using the primary key are very fast, you can construct efficient join queries for such tables. If you set up a numeric ID column for the primary key, use that value to cross-reference with related values in any other tables, ... If ...
https://dev.mysql.com/doc/refman/5.7/en/explain.html
That is, MySQL explains how it would process the statement, including information about how tables are joined and in which order. You can also use EXPLAIN to check whether the optimizer joins the tables in an optimal order. To give a hint to the ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-restarting-group.html
A member cannot join a group if it has transactions that are not present on the other group members. The members with fewer transactions can then join and catch up with the transactions they are missing through distributed recovery. Group ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-the-group.html
The group is dynamic and servers can leave (either voluntarily or involuntarily) and join it at any time. If a server joins the group, it automatically brings itself up to date by fetching the missing state from an existing server. In MySQL Group ...
https://dev.mysql.com/doc/refman/5.7/en/identifier-qualifiers.html
An unqualified name is permitted in contexts where interpretation of the name is unambiguous. A qualified name includes at least one qualifier to clarify the interpretive context by overriding a default context or providing missing context. For ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-best-practices.html
Use joins wherever data is pulled from multiple tables based on identical ID values from those tables. For fast join performance, define foreign keys on the join columns, and declare those columns with the same data type in each table. Specify a ...
https://dev.mysql.com/doc/refman/5.7/en/known-issues.html
For example, the following does not work: mysql> SELECT * FROM temp_table, temp_table AS t2; ERROR 1137: Can't reopen table: 'temp_table' The optimizer may handle DISTINCT differently when you are using “hidden” columns in a join than when you ... This section lists known issues in recent versions of ...
https://dev.mysql.com/doc/refman/5.7/en/myisam-optimization.html
This improves join performance by enabling the join optimizer to better choose the order in which to join the tables and which indexes it should use. To coalesce fragmented rows and eliminate wasted space that results from deleting or updating ...
https://dev.mysql.com/doc/refman/5.7/en/myisamchk-other-options.html
This improves join performance by enabling the join optimizer to better choose the order in which to join the tables and which indexes it should use. myisamchk supports the following options for actions other than table checks and repairs: ...