PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysqldump-copying-database.html
$> mysqldump db1 > dump.sql $> mysqladmin create db2 $> mysql db2 < dump.sql Do not use --databases on the mysqldump command line because that causes USE db1 to be included in the dump file, which overrides the effect of naming db2 on the mysql ...
https://dev.mysql.com/doc/refman/8.0/en/perl-installation.html
For example, to unpack and build a DBI distribution, use a procedure such as this: Unpack the distribution into the current directory: $> gunzip < DBI-VERSION.tar.gz | tar xvf - This command creates a directory named DBI-VERSION. MySQL Perl support ...
https://dev.mysql.com/doc/refman/8.0/en/perror.html
perror displays the error message for MySQL or operating system error codes. For example, for the ER_WRONG_VALUE_FOR_VAR error, perror understands any of these arguments: 1231, 001231, MY-1231, or MY-001231, or ER_WRONG_VALUE_FOR_VAR. The meaning ...
https://dev.mysql.com/doc/refman/8.0/en/point-in-time-recovery-binlog.html
By default, the server creates binary log files in the data directory, but a path name can be specified with the --log-bin option to place the files in a different location. This section explains the general idea of using the binary log to perform ...
https://dev.mysql.com/doc/refman/8.0/en/problems-with-mysql-sock.html
Another approach is to change the place where the server creates the Unix socket file. The default location for the Unix socket file that the server uses for communication with local clients is /tmp/mysql.sock. (For some distribution formats, the ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/en/replication-binlog-encryption-encryption-keys.html
The keyring service handles the creation, retrieval, and deletion of the binary log encryption keys. A server instance only creates and removes keys generated for itself, but it can read keys generated for other instances if they are stored in the ... The binary log encryption keys used to encrypt the file passwords for the log files are 256-bit keys that are generated specifically for each MySQL server instance using MySQL Server's keyring service (see Section 8.4.4, “The MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html
Relay log files are encrypted for all channels, including new channels that are created after encryption is activated. From MySQL 8.0.14, mysqlbinlog returns a suitable error if you attempt to read an encrypted binary log file directly, but older ...
https://dev.mysql.com/doc/refman/8.0/en/replication-configuration.html
This section describes how to configure the different types of replication available in MySQL and includes the setup and configuration required for a replication environment, including step-by-step instructions for creating a new replication ...For ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids.html
This section discusses the following topics: How GTIDs are defined and created, and how they are represented in a MySQL server (see Section 19.1.3.1, “GTID Format and Storage”). This section explains transaction-based replication using global ...