PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/procedure-analyse.html
ANALYSE([max_elements[,max_memory]]) Note PROCEDURE ANALYSE() is deprecated as of MySQL 5.7.18, and is removed in MySQL 8.0. ANALYSE() examines the result from a query and returns an analysis of the results that suggests optimal data types for each ...
https://dev.mysql.com/doc/refman/5.7/en/purge-binary-logs.html
PURGE { BINARY | MASTER } LOGS { TO 'log_name' | BEFORE datetime_expr } The binary log is a set of files that contain information about data modifications made by the MySQL server. The log consists of a set of binary log files, plus an index file ...
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/rename-user.html
RENAME USER old_user TO new_user [, old_user TO new_user] ... An error occurs for old accounts that do not exist or new accounts that already exist. To use RENAME USER, you must have the global CREATE USER privilege, or the UPDATE privilege for the ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs-relaylog.html
The relay log, like the binary log, consists of a set of numbered files containing events that describe database changes, and an index file that contains the names of all used relay log files. The term “relay log file” generally denotes an ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs.html
A replica server creates several repositories of information to use for the replication process: The relay log, which is written by the replication I/O thread, contains the transactions read from the replication source server's binary log. The ...
https://dev.mysql.com/doc/refman/5.7/en/replica-sql-thread-states.html
Making temporary file (create) before replaying LOAD DATA INFILE The thread is executing a LOAD DATA statement and is creating a temporary file containing the data from which the replica reads rows. This state can only be encountered if the original ...
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-create-select.html
SELECT statement to make any changes in tables other than the table that is created by the statement. Some older versions of MySQL permitted these statements to do so; this means that, when using replication between a MySQL 5.6 or later replica and ...
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 ...