Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-benefits.html
Truncating a file-per-table tablespace is very fast and can free up disk space for the operating system to reuse rather than only InnoDB. InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-space.html
For tables stored this way, there is less fragmentation within the disk file, and when the table is truncated, the space is returned to the operating system rather than still being reserved by InnoDB within the system tablespace. The data files ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-migration.html
This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL instance to a larger, faster server; you might clone an entire MySQL instance to a new ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-operations.html
DISCARD PARTITION No No No Only permits ALGORITHM=DEFAULT, LOCK=DEFAULT IMPORT PARTITION No No No Only permits ALGORITHM=DEFAULT, LOCK=DEFAULT TRUNCATE PARTITION No Yes Yes Does not copy existing data. Online support details, syntax examples, and ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-redo-log.html
Redo log data is appended as data modifications occur, and the oldest data is truncated as the checkpoint progresses. The redo log is a disk-based data structure used during crash recovery to correct data written by incomplete transactions. During ...
https://dev.mysql.com/doc/refman/8.4/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.4/en/insert.html
INSERT [LOW_PRIORITY | DELAYED | HIGH_PRIORITY] [IGNORE] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] { {VALUES | VALUE} (value_list) [, (value_list)] ... | TABLE table_name | VALUES ...
https://dev.mysql.com/doc/refman/8.4/en/json-search-functions.html
The functions in this section perform search or comparison operations on JSON values to extract data from them, report whether data exists at a location within them, or report the path to data within them. JSON_CONTAINS(target, candidate[, path]) ...
https://dev.mysql.com/doc/refman/8.4/en/json.html
The conversion to number should produce a meaningful result for JSON values that are numeric scalars, although (depending on the values) truncation and loss of precision may occur. The JSON data type provides these advantages over storing ...
https://dev.mysql.com/doc/refman/8.4/en/keyring-functions-general-purpose.html
A key value longer than that length can be stored using a keyring service function (see Section 7.6.9.2, “The Keyring Service”), but if retrieved using keyring_key_fetch() is truncated to the general keyring function limit. MySQL Server ...