PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndb-api-statistics.html
This reflects the creation of the hidden primary key that is a feature of all tables using the NDB storage engine. A number of types of statistical counters relating to actions performed by or affecting Ndb objects are available. Such actions ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-online-add-node-remarks.html
However, all data and indexes added to tables created after a new node group has been added are distributed automatically among all cluster data nodes, including those added as part of the new node group. Normal DML operations using NDB Cluster data ... This section provides general information about the behavior of and current limitations in adding NDB Cluster nodes ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-privilege-synchronization.html
A statement granting the NDB_STORED_USER privilege, such as GRANT NDB_STORED_USER ON *.* TO 'cluster_app_user'@'localhost', works by directing NDB to create a snapshot using the queries SHOW CREATE USER cluster_app_user@localhost and SHOW GRANTS FOR ... NDB 8.0 introduces a new mechanism for sharing and synchronizing users, roles, and privileges between SQL nodes connected to an NDB ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-blob-tool.html
This tool can be used to check for and remove orphaned BLOB column parts from NDB tables, as well as to generate a file listing any orphaned parts. It is sometimes useful in diagnosing and repairing corrupted or damaged NDB tables containing BLOB ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-upgrade.html
An error occurs if a sys schema exists but has no version view, on the assumption that its absence indicates a user-created schema: A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the ...
https://dev.mysql.com/doc/refman/8.0/en/mysqldump-copying-to-other-server.html
On Server 2: $> mysql < dump.sql Use of --databases with the mysqldump command line causes the dump file to include CREATE DATABASE and USE statements that create the database if it does exist and make it the default database for the reloaded data.
https://dev.mysql.com/doc/refman/8.0/en/mysqldump-definition-data-dumps.html
The --no-data option tells mysqldump not to dump table data, resulting in the dump file containing only statements to create the tables. Conversely, the --no-create-info option tells mysqldump to suppress CREATE statements from the output, so that ...
https://dev.mysql.com/doc/refman/8.0/en/nontransactional-tables.html
This can happen if you try to create a table using a transactional storage engine that is not supported by your mysqld server (or that was disabled with a startup option). If mysqld does not support a storage engine, it instead creates the table as ... If you receive the following message when trying to perform a ROLLBACK, it means that one or more of the tables you used in the transaction do not support transactions: Warning: Some non-transactional changed tables couldn't be rolled back These nontransactional tables are not affected by the ROLLBACK ...
https://dev.mysql.com/doc/refman/8.0/en/online-ddl-memory-management.html
Online DDL operations that create or rebuild secondary indexes allocate temporary buffers during different phases of index creation. The setting applies to buffers created by threads executing online DDL operations. Defining an appropriate buffer ...The innodb_ddl_buffer_size variable, introduced in MySQL 8.0.27, defines the maximum buffer size for online DDL ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-queries.html
To tune queries for InnoDB tables, create an appropriate set of indexes on each table. Do not create a separate secondary index for each column, because each query can only make use of one index. If you have many queries for the same table, testing ...Follow these guidelines for InnoDB indexes: Because each InnoDB table has a primary key (whether you request one or not), specify a set of primary key columns for each table, columns that are used in the most important and time-critical ...