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/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/range-optimization.html
For UPDATE and DELETE statements, if the optimizer falls back to a full table scan and the sql_safe_updates system variable is enabled, an error occurs rather than a warning because, in effect, no key is used to determine which rows to modify. The ...
https://dev.mysql.com/doc/refman/5.7/en/replace-third-party-yum.html
For supported Yum-based platforms (see Section 2.5.1, “Installing MySQL on Linux Using the MySQL Yum Repository”, for a list), you can replace a third-party distribution of MySQL with the latest GA release (from the MySQL 5.7 series currently) ...
https://dev.mysql.com/doc/refman/5.7/en/replica-io-thread-states.html
The I/O thread is waiting until the SQL thread frees enough space by processing relay log contents so that it can delete some relay log files. The following list shows the most common states you see in the State column for a replica server I/O ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs-status.html
To address this, modify the file in a text editor by deleting the initial line containing the number of lines. A replica server creates two replication metadata repositories, the connection metadata repository and the applier metadata repository.
https://dev.mysql.com/doc/refman/5.7/en/replication-features-limit.html
Statement-based replication of LIMIT clauses in DELETE, UPDATE, and INSERT ... SELECT statements is unsafe since the order of the rows affected is not defined. (Such statements can be replicated correctly with statement-based replication only if ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-load-data.html
If you do use LOAD DATA statements with statement-based binary logging, you should delete the temporary files yourself after you no longer need the statement log. LOAD DATA is considered unsafe for statement-based logging (see Section 16.2.1.3, ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-optimizer.html
(In general, this is not a good practice, even outside of replication.) Examples of nondeterministic statements include DELETE or UPDATE statements that use LIMIT with no ORDER BY clause; see Section 16.4.1.17, “Replication and LIMIT”, for a ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-repair-table.html
When used on a corrupted or otherwise damaged table, it is possible for the REPAIR TABLE statement to delete rows that cannot be recovered. However, any such modifications of table data performed by this statement are not replicated, which can ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-triggers.html
(Bug #45677) A trigger can have triggers for different combinations of trigger event (INSERT, UPDATE, DELETE) and action time (BEFORE, AFTER), but before MySQL 5.7.2 cannot have multiple triggers that have the same trigger event and action time.