PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.3Kb
Man Pages (Zip)
- 402.5Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
To investigate database page corruption, you might dump your tables from the database with SELECT ... Usually, most of the data obtained in this way is intact. Serious corruption might cause SELECT * FROM tbl_name statements or InnoDB background ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html
InnoDB Startup Options InnoDB System Variables System variables that are true or false can be enabled at server startup by naming them, or disabled by using a --skip- prefix. For example, to enable or disable the InnoDB adaptive hash index, you can ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-troubleshooting-recovery.html
From MySQL 8.0.26, checkpoints and advancing the checkpoint LSN are not permitted until redo log recovery is complete and data dictionary dynamic metadata (srv_dict_metadata) is transferred to data dictionary table (dict_table_t) objects. If an ...
https://dev.mysql.com/doc/refman/8.0/en/bug-reports.html
Before posting a bug report about a problem, please try to verify that it is a bug and that it has not been reported already: Start by searching the MySQL online manual at https://dev.mysql.com/doc/. We try to keep the manual up to date by updating ...
https://dev.mysql.com/doc/refman/8.0/en/drop-table.html
Be careful with this statement! For each table, it removes the table definition and all table data. If the table is partitioned, the statement removes the table definition, all its partitions, all data stored in those partitions, and all partition ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-recovery.html
To achieve point-in-time recovery after restoring a backup, you can apply changes from the binary log that occurred after the backup was made. Recovery from Data Corruption or Disk Failure If your database becomes corrupted or disk failure occurs, ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html
The redo log is a disk-based data structure used during crash recovery to correct data written by incomplete transactions. During normal operations, the redo log encodes requests to change table data that result from SQL statements or low-level API ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-transaction-management.html
To optimize InnoDB transaction processing, find the ideal balance between the performance overhead of transactional features and the workload of your server. For example, an application might encounter performance issues if it commits thousands of ...
https://dev.mysql.com/doc/refman/8.0/en/rebuilding-tables.html
This section describes how to rebuild or repair tables or indexes, which may be necessitated by: Changes to how MySQL handles data types or character sets. For example, an error in a collation might have been corrected, necessitating a table ...
https://dev.mysql.com/doc/refman/8.0/en/server-option-variable-reference.html
The following table lists all command-line options, system variables, and status variables applicable within mysqld. The table lists command-line options (Cmd-line), options valid in configuration files (Option file), server system variables ...