Outils pour utilisateurs
linux:mysql (lu 65374 fois)
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente | Prochaine révision Les deux révisions suivantes | ||
|
linux:mysql [09-10-2019 16:40] edmc73 |
linux:mysql [09-02-2020 21:14] edmc73 [Sauvegarder] |
||
|---|---|---|---|
| Ligne 53: | Ligne 53: | ||
| Sauvegarder toutes les tables avec un prefix | Sauvegarder toutes les tables avec un prefix | ||
| mysqldump -h hostname -u user -p $(mysql nom_de_la_base -h hostname -u user -p -Bse 'show tables like" | mysqldump -h hostname -u user -p $(mysql nom_de_la_base -h hostname -u user -p -Bse 'show tables like" | ||
| + | |||
| + | La bonne pratique en prod est d' | ||
| + | |||
| + | mysqldump -u USER -p --single-transaction --quick --lock-tables=false --all-databases (or) DATABASE | gzip > OUTPUT.sql.gz | ||
| + | |||
| + | * --quick : This option is useful for dumping large tables. It forces mysqldump to retrieve rows for a table from the server a row at a time rather than retrieving the entire row set and buffering it in memory before writing it out | ||
| + | |||
| + | * --single-transaction : This option sets the transaction isolation mode to REPEATABLE READ and sends a START TRANSACTION SQL statement to the server before dumping data. It is useful only with transactional tables such as InnoDB, because then it dumps the consistent state of the database at the time when START TRANSACTION was issued without blocking any applications. | ||
| + | |||
| + | * --lock-tables=false : option stops MyISAM tables (if they exsit) being locked during the backup | ||
| Restaurer | Restaurer | ||
linux/mysql.txt · Dernière modification: 14-02-2023 11:39 de edmc73
Outils de la page
