Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.4(EOL), 10.5, 10.6, 10.9(EOL), 10.10(EOL), 10.11
-
Debian GNU/Linux 10 (buster)
Description
If you have binlog enabled and binlog_do_db set to some table and then make a mariadb-dump and import the dump to some database different of the one set in binlog_do_db, then all the Innodb tables in that database have no records.
I'm attaching a bash script to demonstrate the problem.
The result from all counts should e 1, but when binlog_do_db is set the result for the innodb table changes.
That behaviour wasn't observed in 10.5 versions. It appeared after upgrade to 10.8.
Cannot report for the versions in between, unfortunately.
Attachments
Issue Links
- is duplicated by
-
MDEV-30834 restoring a dump created by mysqldump doesn't restore table rows if the database is excluded from binary log using binlog_ignore_db option
- Closed
-
MDEV-32442 Tables empty after mysqldump restore when binlog_do_db is set for a different db
- Closed
- relates to
-
MDEV-24621 In bulk insert, pre-sort and build indexes one page at a time
- Closed