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/replication-features-flush.html
Some forms of the FLUSH statement are not logged because they could cause problems if replicated to a replica: FLUSH LOGS and FLUSH TABLES WITH READ LOCK. The FLUSH TABLES, ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE statements are written to ...These statements are written to the binary log unless you specify NO_WRITE_TO_BINLOG or its alias ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-config-nodes.html
The config_nodes table shows nodes configured in an NDB Cluster config.ini file. For each node, the table displays a row containing the node ID, the type of node (management node, data node, or API node), and the name or IP address of the host on ...The node_type column displays one of the following three values: MGM: Management ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-logbuffers.html
The logbuffer table provides information on NDB Cluster log buffer usage. The logbuffers table contains the following columns: node_id The ID of this data node. One each of these log_type rows is shown in the logbuffers table for each data node in ...One of these rows has the log type BACKUP-DATA, which shows the amount of data buffer used during backup to copy fragments to backup ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-processes.html
This table contains information about NDB Cluster node processes; each node is represented by the row in the table. Only nodes that are connected to the cluster are shown in this table. You can obtain information about nodes that are configured but ...The node_type column displays one of the following three values: MGM: Management ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-threadstat.html
The threadstat table provides a rough snapshot of statistics for threads running in the NDB kernel. Since this table contains counts taken at a given point in time, for best results it is necessary to query this table periodically and store the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-directory.html
If a DATA DIRECTORY or INDEX DIRECTORY table option is used in a CREATE TABLE statement on the source server, the table option is also used on the replica. This can be overridden by using the NO_DIR_IN_CREATE server SQL mode on the replica, which ...This can cause problems if no corresponding directory exists in the replica host's file system or if it exists but is not accessible to the replica ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-truncate.html
TRUNCATE TABLE is normally regarded as a DML statement, and so would be expected to be logged and replicated using row-based format when the binary logging mode is ROW or MIXED. However this caused issues when logging or replicating, in STATEMENT ...
https://dev.mysql.com/doc/refman/5.7/en/subquery-optimization.html
Note A limitation on UPDATE and DELETE statements that use a subquery to modify a single table is that the optimizer does not use semijoin or materialization subquery optimizations. As a workaround, try rewriting them as multiple-table UPDATE and ...
https://dev.mysql.com/doc/refman/5.7/en/deleting-from-related-tables.html
If the total length of the DELETE statement for related_table is more than 1MB (the default value of the max_allowed_packet system variable), you should split it into smaller parts and execute multiple DELETE statements. You probably get the ...
https://dev.mysql.com/doc/refman/5.7/en/table-definition-issues.html
...