Search Results
https://dev.mysql.com/doc/refman/8.4/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.4/en/mysql-cluster-programs-ndb-desc.html
ndb_desc provides a detailed description of one or more NDB tables. Usage ndb_desc -c connection_string tbl_name -d db_name [options] ndb_desc -c connection_string index_name -d db_name -t tbl_name Additional options that can be used with ndb_desc ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-programs-ndb-import.html
--errins-type=name Command-Line Format --errins-type=name Type Enumeration Default Value [none] Valid Values stopjobstopallsighupsigintlist Error insert type; use list as the name value to obtain all possible values. --errins-delay=# Command-Line ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-mta.html
Conversely, transactions performing inserts, updates and deletes on foreign key child tables (referencing) are not especially serialized with regard to one another. To use this functionality with NDB Cluster, it is necessary that the replica be ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-nutshell.html
Firewall stored procedures now avoid performing unnecessary combinations of DELETE plus INSERT statements, as well as those of INSERT IGNORE plus UPDATE operations, thus consuming less time and fewer resources, making them faster and more efficient.
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-transaction-management.html
Avoid performing rollbacks after inserting, updating, or deleting huge numbers of rows. Set innodb_change_buffering=all so that update and delete operations are buffered in addition to inserts. To optimize InnoDB transaction processing, find the ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-info.html
When insertions, deletions, or updates are made to partitioned tables, the binary log records information about the partition and (if any) the subpartition in which the row event took place. This section discusses obtaining information about ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-pruning.html
An INSERT statement also accesses only one partition per inserted row; this is true even for a table that is partitioned by HASH or KEY although this is not currently shown in the output of EXPLAIN. The optimization known as partition pruning is ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-range.html
A table that is partitioned by range is partitioned in such a way that each partition contains rows for which the partitioning expression value lies within a given range. Ranges should be contiguous but not overlapping, and are defined using the ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-types.html
With this type of partitioning, a partition is selected based on the value returned by a user-defined expression that operates on column values in rows to be inserted into the table. When a new row is inserted into a partitioned table, it is these ... This section discusses the types of partitioning which are available in MySQL ...