Bug #18114 | Server crash when doing mysqldump | ||
---|---|---|---|
Submitted: | 9 Mar 2006 19:51 | Modified: | 20 Mar 2006 22:45 |
Reporter: | Markus Popp | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.0.19-max-nt | OS: | Windows (Windows) |
Assigned to: | CPU Architecture: | Any |
[9 Mar 2006 19:51]
Markus Popp
[20 Mar 2006 22:10]
MySQL Verification Team
I was unable to repeat this issue on Suse Linux, will try on Windows with the same source: miguel@hegel:~/dbs/5.0> bin/mysqldump --add-drop-table --complete-insert --default-character-set=utf8 --all-databases --triggers=false -h loca lhost -u mpopp -p 1>"/home/miguel/s/dump.sql" Enter password: miguel@hegel:~/dbs/5.0> ls /home/miguel/s/dump.sql -la -rw-r--r-- 1 miguel users 307044 2006-03-20 19:09 /home/miguel/s/dump.sql
[20 Mar 2006 22:16]
MySQL Verification Team
On Windows with 5.0.19 it crashes, will see with current source server: c:\mysql\bin>mysqldump --add-drop-table --complete-insert --default-character-set=utf8 --all-databases --triggers=fals e -h localhost -u mpopp -p 1>"c:\temp\dump.sql" Enter password: mysqldump: mysqldump: Couldn't execute 'SHOW CREATE TABLE `v_tagesauswertung`': MySQL server has gone away (2006)
[20 Mar 2006 22:45]
MySQL Verification Team
Thank you for the bug report. Testing against latest source on Linux and Windows I was unable to repeat. Then please wait for the next release: c:\mysql\bin>mysqldump --add-drop-table --complete-insert --default-character-set=utf8 --all-databases --triggers=fals e -h localhost -u mpopp -p 1>"c:\temp\dump.sql" Enter password: c:\mysql\bin>dir c:\temp\dump.sql O volume na unidade C não tem nome. O número de série do volume é D427-8BBE Pasta de c:\temp 20/03/2006 19:42 307.707 dump.sql 1 arquivo(s) 307.707 bytes 0 pasta(s) 16.681.422.848 bytes disponíveis c:\mysql\bin>