PDF (US Ltr)
- 43.1Mb
PDF (A4)
- 43.2Mb
Man Pages (TGZ)
- 296.0Kb
Man Pages (Zip)
- 401.3Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/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.0/en/innodb-benefits.html
InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless of what was happening in the database at the time, you don't need to do anything special after restarting the database.
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-usage.html
Compressed tables can be created in file-per-table tablespaces or in general tablespaces. The system tablespace (space 0, the .ibdata files) can contain user-created tables, but it also contains internal system data, which is never compressed.
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-defragmenting.html
Random insertions into or deletions from a secondary index can cause the index to become fragmented. Fragmentation means that the physical ordering of the index pages on the disk is not close to the index ordering of the records on the pages, or ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-space.html
The data files that you define in the configuration file using the innodb_data_file_path configuration option form the InnoDB system tablespace. You cannot define where within the system tablespace your tables are allocated. In a newly created ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Key ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-developing.html
Typically, writing an application for the InnoDB memcached plugin involves some degree of rewriting or adapting existing code that uses MySQL or the memcached API. With the daemon_memcached plugin, instead of many traditional memcached servers ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-intro.html
The InnoDB memcached plugin implements memcached as a MySQL plugin daemon that accesses the InnoDB storage engine directly, bypassing the MySQL SQL layer. The following diagram illustrates how an application accesses data through the ...
https://dev.mysql.com/doc/refman/8.0/en/insert-optimization.html
To optimize insert speed, combine many small operations into a single large operation. Ideally, you make a single connection, send the data for many new rows at once, and delay all index updates and consistency checking until the very end. The size ...
https://dev.mysql.com/doc/refman/8.0/en/internal-temporary-tables.html
In some cases, the server creates internal temporary tables while processing statements. The server creates temporary tables under conditions such as these: Evaluation of UNION statements, with some exceptions described later. Evaluation of some ...