Bug #12129 | mysqldump on the master breaks replication and creates "interesting" dump | ||
---|---|---|---|
Submitted: | 23 Jul 2005 10:41 | Modified: | 25 Oct 2005 10:44 |
Reporter: | Victoria Reznichenko | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.0.11-beta-debug-log | OS: | Any (any) |
Assigned to: | Bugs System | CPU Architecture: | Any |
[23 Jul 2005 10:41]
Victoria Reznichenko
[23 Jul 2005 10:46]
MySQL Verification Team
just changed synopsis a bit.
[27 Aug 2005 19:09]
Patrick Galbraith
There are some other bugs logged about mysqldump not handling (such as 10322) that list mysqldump not being able to handle views properly, and I need to see if this bug has any dependency or relation
[14 Oct 2005 23:52]
Patrick Galbraith
I have a fix for BUG# 12838 that I want to test against this.
[19 Oct 2005 5:41]
Patrick Galbraith
Patch for BUG# 12838 fixes this: patg@krsna:~/mysql-build/mysql-5.0.test1/client> ./mysqldump --master-data=2 -u root -S /tmp/mysqld-5.0-master.sock test > test.sql mysqldump: mysqldump: Couldn't execute 'CREATE TEMPORARY TABLE `v0` SELECT * FROM `v0` WHERE 0': Can't execute the query because you have a conflicting read lock (1223) With patch for BUG# 12838 patg@krsna:~/mysql-build/mysql-5.0.test1/client> ./mysqldump --master-data=2 -u root -S /tmp/mysqld-5.0-master.sock test > test.sql (no errors)
[25 Oct 2005 10:44]
Sergei Golubchik
duplicate of BUG#12838