PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/optimizer-trace-implementation.html
A trace is started by creating an instance of Opt_trace_start; information is added to this trace by creating instances of Opt_trace_object and Opt_trace_array, and by using the add() methods of these classes.
https://dev.mysql.com/doc/refman/8.0/en/password-security-user.html
However, this method of entering a password is suitable only for programs that you run interactively. By default, this file is named .mysql_history and is created in your home directory. Passwords can be written as plain text in SQL statements such ... MySQL users should use the following guidelines to keep passwords ...
https://dev.mysql.com/doc/refman/8.0/en/preface.html
It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. Use of this documentation is subject to the following terms: You may create a printed copy of this ...
https://dev.mysql.com/doc/refman/8.0/en/rename-user.html
To use RENAME USER, you must have the global CREATE USER privilege, or the UPDATE privilege for the mysql system schema. However, RENAME USER does not automatically drop or invalidate databases or objects within them that the old user created.
https://dev.mysql.com/doc/refman/8.0/en/replica-logs-relaylog.html
Successive relay log files are created using successive sequence numbers, beginning with 000001. On a Unix system, this can be done as shown here: $> cat new_relay_log_name.index >> old_relay_log_name.index $> mv old_relay_log_name.index ... The ...
https://dev.mysql.com/doc/refman/8.0/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. The following list shows the most common states ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-key-rotation.html
If the server UUID changes, for example because a backup created using MySQL Enterprise Backup is used to set up a new replica, issuing ALTER INSTANCE ROTATE BINLOG MASTER KEY on the new server does not delete any earlier binary log encryption keys ... When binary log encryption is enabled, you can rotate the binary log master key at any time while the server is running by issuing ALTER INSTANCE ROTATE BINLOG MASTER ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-scope.html
Note If you use LOAD DATA when binlog_format=STATEMENT is set, which is not recommended as the statement is considered unsafe for statement-based replication, a temporary file containing the data is created on the replica where the changes are ...
https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-performance.html
Also, as each replica must receive a full copy of the source's binary log, the network load on the source may also increase and create a bottleneck. One way to improve the performance of the replication process is to create a deeper replication ...
https://dev.mysql.com/doc/refman/8.0/en/savepoint.html
A new savepoint level is created when a stored function is invoked or a trigger is activated. When the function or trigger terminates, any savepoints it created are released and the previous savepoint level is restored. SAVEPOINT identifier ...