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/innodb-compression-usage.html
For general tablespaces, keep in mind that dropping a table does not reduce the size of the general tablespace .ibd file, nor does it return disk space to the operating system. Compressed tables can be created in file-per-table tablespaces or in ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-defragmenting.html
Another way to perform a defragmentation operation is to use mysqldump to dump the table to a text file, drop the table, and reload it from the dump file. Random insertions into or deletions from a secondary index can cause the index to become ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-physical-structure.html
If the fill factor of an InnoDB index page drops below the MERGE_THRESHOLD, which is 50% by default if not specified, InnoDB tries to contract the index tree to free the page. With the exception of spatial indexes, InnoDB indexes are B-tree data ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-system-tablespace.html
Unlike the system tablespace, file-per-table tablespaces return disk space to the operating system when they are truncated or dropped. The system tablespace is the storage area for the change buffer. It may also contain table and index data if ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-truncate-table-reclaim-space.html
When a table is truncated, it is dropped and re-created in a new .ibd file, and the freed space is returned to the operating system. To reclaim operating system disk space when truncating an InnoDB table, the table must be stored in its own .ibd ...
https://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html
Dropping and re-adding an index can be expensive for a large table, whereas making it invisible and visible are fast, in-place operations. MySQL supports invisible indexes; that is, indexes that are not used by the optimizer. The feature applies to ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-log-events.html
Table 25.61 Events relating to NDB Cluster schema operations Event Priority Severity Level Description CreateSchemaObject 8 INFO Schema objected created AlterSchemaObject 8 INFO Schema object updated DropSchemaObject 8 INFO Schema object dropped ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-logs-cluster-log.html
The following table lists the most common NDB cluster log messages. For information about the cluster log, log events, and event types, see Section 25.6.3, “Event Reports Generated in NDB Cluster”. These log messages also correspond to log ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-events.html
This table provides information about event subscriptions in NDB. The columns of the events table are listed here, with short descriptions of each: event_id The event ID name The name of the event table_id The ID of the table on which the event ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-perror.html
This is intended as a drop-in replacement for perror --ndb, which is no longer supported. ndb_perror shows information about an NDB error, given its error code. This includes the error message, the type of error, and whether the error is permanent ...