Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-backup.html
The key to safe database management is making regular backups. Hot and cold backups are physical backups that copy actual data files, which can be used directly by the mysqld server for faster restore. Using MySQL Enterprise Backup is the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-background.html
The compressed page size is specified through the CREATE TABLE or ALTER TABLE KEY_BLOCK_SIZE parameter. The level of compression is the same regardless of the KEY_BLOCK_SIZE value. As you specify smaller values for KEY_BLOCK_SIZE, you get the I/O ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning-monitoring.html
The INNODB_CMP table reports information about compression activity for each compressed page size (KEY_BLOCK_SIZE) in use. The key statistics to consider are the number of, and amount of time spent performing, compression and uncompression ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-error-handling.html
A duplicate-key error rolls back the SQL statement, if you have not specified the IGNORE option in your statement. InnoDB sometimes rolls back only the statement that failed, other times it rolls back the entire transaction. If you run out of file ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-per-table-tablespaces.html
A file-per-table tablespace contains data and indexes for a single InnoDB table, and is stored on the file system in a single data file. File-per-table tablespace characteristics are described under the following topics in this section: ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-init-startup-configuration.html
For example, if you use MyISAM tables, consider the amount of memory allocated for the key buffer (key_buffer_size). innodb_buffer_pool_size + key_buffer_size + max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size) + ... The first ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-locking-transaction-model.html
Section 17.7.4, “Phantom Rows” describes how InnoDB uses next-key locking to avoid phantom rows. To implement a large-scale, busy, or highly reliable database application, to port substantial code from a different database system, or to tune ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-failure-conditions.html
For example, you might insert duplicate values into a column while a unique index is being created, or you might insert NULL values into a column while creating a primary key index on that column. The failure of an online DDL operation is typically ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl.html
For example: ALTER TABLE tbl_name ADD PRIMARY KEY (column), ALGORITHM=INPLACE; The LOCK clause may be used for operations that are performed in place and is useful for fine-tuning the degree of concurrent access to the table during operations. The ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-page-compression.html
InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Page compression is enabled by specifying the COMPRESSION attribute with CREATE TABLE or ALTER TABLE. Supported Platforms Page compression requires sparse ...