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/change-replication-source-to.html
OFF: The replica sets sql_require_primary_key = OFF; no replicated CREATE TABLE or ALTER TABLE statement is checked for the presence of a primary key. If you are using statement-based replication and temporary tables, it is possible for a CHANGE ...
https://dev.mysql.com/doc/refman/8.0/en/connection-control-information-schema-tables.html
The following sections describe the INFORMATION_SCHEMA tables associated with the connection_control plugin.
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-compression-tables.html
There are two pairs of InnoDB INFORMATION_SCHEMA tables about compression that can provide insight into how well compression is working overall: INNODB_CMP and INNODB_CMP_RESET provide information about the number of compression operations and the ...INNODB_CMPMEM and INNODB_CMPMEM_RESET provide information about the way memory is allocated for ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-tables.html
This section covers topics related to InnoDB tables. ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-table-problems.html
The file format that MySQL uses to store data has been extensively tested, but there are always circumstances that may cause database tables to become corrupted. The following discussion describes how this can happen and how to handle it.
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-keyring-tables.html
The following sections describe the Performance Schema tables associated with the MySQL keyring (see Section 8.4.4, “The MySQL Keyring”). They provide information about keyring operation: keyring_component_status: Information about the keyring ...
https://dev.mysql.com/doc/refman/8.0/en/sys-schema-tables.html
The following sections describe sys schema tables and triggers. ...
https://dev.mysql.com/doc/refman/8.0/en/federated-create-connection.html
To use the first method, you must specify the CONNECTION string after the engine type in a CREATE TABLE statement. For example: CREATE TABLE federated_table ( id INT(20) NOT NULL AUTO_INCREMENT, name VARCHAR(32) NOT NULL DEFAULT '', other INT(20) ...The format of the connection string is as follows: scheme://user_name[:password]@host_name[:port_num]/db_name/tbl_name Where: scheme: A recognized connection ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-files-table.html
The Information Schema FILES table provides metadata about all InnoDB tablespace types including file-per-table tablespaces, general tablespaces, the system tablespace, temporary table tablespaces, and undo tablespaces (if present). For more ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-optimization.html
To coalesce fragmented rows and eliminate wasted space that results from deleting or updating rows, run myisamchk in recovery mode: $> myisamchk -r tbl_name You can optimize a table in the same way by using the OPTIMIZE TABLE SQL statement.