Bug #60902 mysqldump does not dump the replication *_info tables
| Submitted: | 18 Apr 2011 6:05 | Modified: | 17 Oct 2011 18:50 |
|---|---|---|---|
| Reporter: | Giuseppe Maxia | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: mysqldump Command-line Client | Severity: | S2 (Serious) |
| Version: | 5.6.2 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | dump, replication, table | ||
[18 Apr 2011 6:05]
Giuseppe Maxia
[18 Apr 2011 11:33]
Valeriy Kravchuk
Thank you for the bug report. Verified just as described on Windows XP.
[17 Oct 2011 18:50]
Jon Stephens
Documented bugfix in the 5.6.4 changelog as follows:
mysqldump --all-databases
(http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_all-databases) did not dump the
replication log tables. (They could be dumped only by
naming them explicitly when invoking mysqldump, and using
the --master-data
(http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_master-data) option.)
As a result of the fix for this problem, it is now
possible to execute statements requiring read locks on
the replication log tables at any time, while any
statements requiring a write lock on either or both of
these tables are disallowed whenever replication is in
progress. For more information, see Replication Relay and
Status Logs
(http://dev.mysql.com/doc/refman/5.6/en/slave-logs.html).
(Bug #12402875, Bug #60902)
Also updated the descriptions of the slave log tables and the mysqldump
--all-databases and --master-data options in the 5.6 Manual.
Closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.