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/slow-query-log.html
The slow query log can be used to find queries that take a long time to execute and are therefore candidates for optimization. By default, administrative statements are not logged, nor are queries that do not use indexes for lookups. This behavior ... The slow query log consists of SQL statements that take more than long_query_time seconds to execute and require at least min_examined_row_limit rows to be ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-configuration.html
For example, a client can disable use of the query cache for its own queries like this: mysql> SET SESSION query_cache_type = OFF; If you set query_cache_type at server startup (rather than at runtime with a SET statement), only the numeric values ... Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache.html
The query cache can be useful in an environment where you have tables that do not change very often and for which the server receives many identical queries. Note The query cache is not supported for partitioned tables, and is automatically disabled ... Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-operation.html
Incoming queries are compared to those in the query cache before parsing, so the following two queries are regarded as different by the query cache: SELECT * FROM tbl_name Select * from tbl_name Queries must be exactly the same (byte for byte) to be ... Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/query-log.html
However, further logging of queries to the file does not occur unless the FILE log destination is selected. If the destination is NONE, the server writes no queries even if the general log is enabled. The general query log is a general record of ...
https://dev.mysql.com/doc/refman/5.7/en/entering-queries.html
At this point, it is more important to find out a little about how to issue queries than to jump right in creating tables, loading data into them, and retrieving data from them. This section describes the basic principles of entering queries, using ... Make sure that you are connected to the server, as discussed in the previous ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html
However, if two or more queries use the same table, only one table block needs to be allocated. It counts the number of queries that have been removed from the cache to free up memory for caching new queries. The query cache uses a least recently ...
https://dev.mysql.com/doc/refman/5.7/en/log-destinations.html
However, further logging of queries to the file does not occur unless the FILE log destination is selected. This enables the use of queries that select only those log entries that satisfy specific criteria. For example, to select log contents ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-thread-states.html
These thread states are associated with the query cache (see Section 8.10.3, “The MySQL Query Cache”). checking privileges on cached query The server is checking whether the user has privileges to access a cached query result. checking query ...
https://dev.mysql.com/doc/refman/5.7/en/controlling-query-plan-evaluation.html
For join queries, the number of possible plans investigated by the MySQL optimizer grows exponentially with the number of tables referenced in a query. However, when larger queries are submitted, the time spent in query optimization may easily ...