Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.0.20
-
None
-
Debian Jessie X64
Description
When doing a full DB dump with mysqldump some tables are dumped regardles of their appearance in --ignore-table.
/usr/bin/mysqldump --defaults-file=/etc/mysql/mydump.cnf -u<user> -p<password> --add-locks --extended-insert --add-locks --add-drop-database --add-drop-table --single-transaction --routines --triggers --all-databases --all-tablespaces --allow-keywords --complete-insert --create-options --events --dump-date>/root/db.sql
cat /etc/mysql/mydump.cnf
[mysqldump]
|
ignore-table=mysql.general_log
|
ignore-table=mysql.slow_log
|
Still contains the two tables, other mysql.* tables can be ignored, worse in some cases it also contains the drop statement which causes an import to fail! (when dumping the whole server the export includes "/!40000 DROP DATABASE IF EXISTS `mysql`/;" which breaks if we attempt to import it).
Attachments
Issue Links
- relates to
-
MDEV-4875 Can't restore a mysqldump if --add-drop-database meets general_log
- Closed
- links to