Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/_static/expand-fast-creation.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/_static/technical-view-fast-creation.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
10 changes: 10 additions & 0 deletions docs/extended-mysqldump.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,16 @@ More information can be found in [Backup Locks](backup-locks.md).
More information can be found in
[Compressed columns with dictionaries](compressed-columns.md).

## `InnoDB` secondary keys and `--innodb-optimize-keys`

For *InnoDB* tables, `--innodb-optimize-keys` omits secondary keys (and related
constraints) from the initial `CREATE TABLE` in the dump and adds them in a
follow-up `ALTER TABLE` after the data is loaded. That pattern works well when
the target server can build those indexes using [expanded fast index
creation](innodb-expanded-fast-index-creation.md). See that page for
limitations (foreign keys, partitioned tables, `AUTO_INCREMENT`, implicit
primary keys, and others) and for the `expand_fast_index_creation` variable.

## Taking backup by descending primary key order

–order-by-primary-desc tells `mysqldump` to take the backup by
Expand Down
Loading