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/processlist-access.html
db is the default database for the thread, or NULL if none has been selected. The following discussion enumerates the sources of process information, the privileges required to see process information, and describes the content of process list ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html
Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL 8.0. To check whether the query cache is present in your MySQL server, use the following statement: mysql> SHOW VARIABLES LIKE 'have_query_cache'; ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-thread-states.html
This can happen for any statement that needs to perform some query cache operation, such as an INSERT or DELETE that invalidates the query cache, a SELECT that looks for a cached entry, RESET QUERY CACHE, and so forth. These thread states are ...
https://dev.mysql.com/doc/refman/5.7/en/reloading-sql-format-dumps.html
To reload a dump file written by mysqldump that consists of SQL statements, use it as input to the mysql client.
https://dev.mysql.com/doc/refman/5.7/en/repair-table.html
[QUICK] [EXTENDED] [USE_FRM] REPAIR TABLE repairs a possibly corrupted table, for certain storage engines only. Although normally you should never have to run REPAIR TABLE, if disaster strikes, this statement is very likely to get back all your data ...
https://dev.mysql.com/doc/refman/5.7/en/repeat.html
[begin_label:] REPEAT statement_list UNTIL search_condition END REPEAT [end_label] The statement list within a REPEAT statement is repeated until the search_condition expression is true. statement_list consists of one or more statements, each ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-auto-increment.html
Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID(), and TIMESTAMP values is done correctly, subject to the following exceptions: When using statement-based replication prior to MySQL 5.7.1, AUTO_INCREMENT columns in tables on the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-limit.html
SELECT statements is unsafe since the order of the rows affected is not defined. Statement-based replication of LIMIT clauses in DELETE, UPDATE, and INSERT ... (Such statements can be replicated correctly with statement-based replication only if ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-memory.html
SELECT FROM memory_table may insert a different set of rows on the source and replica. When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-auto-positioning.html
This GTID set is equal to the union of the set of GTIDs in the gtid_executed system variable (@@GLOBAL.gtid_executed), and the set of GTIDs recorded in the Performance Schema replication_connection_status table as received transactions (the result ... GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and ...