| Bug #34027 | Backup: crash if long longblob | ||
|---|---|---|---|
| Submitted: | 24 Jan 2008 1:15 | Modified: | 12 Sep 2008 7:03 |
| Reporter: | Peter Gulutzan | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S1 (Critical) |
| Version: | 6.0.5-alpha-debug | OS: | Linux (SUSE 10 / 64-bit) |
| Assigned to: | Rafal Somla | CPU Architecture: | Any |
[26 Jan 2008 7:13]
Sveta Smirnova
Thank you for the report. Verified as described.
[1 Sep 2008 9:34]
Jørgen Løland
May be related to bug#37212
[12 Sep 2008 7:03]
Rafal Somla
Can not repeat the failure in the current mysql-6.0-backup tree. The tree contains a patch for BUG#37212 which apparently also fixes this issue.

Description: I create a table with a longblob with 10,000,000 bytes. I say BACKUP DATABASE. Crash. How to repeat: mysql> create database y; Query OK, 1 row affected (0.00 sec) mysql> use y Database changed mysql> create table t (s1 longblob) engine=falcon; Query OK, 0 rows affected (0.30 sec) mysql> set @@max_allowed_packet = 50000000; Query OK, 0 rows affected (0.00 sec) mysql> insert into t values (repeat('a',10000000)); Query OK, 1 row affected (13.39 sec) mysql> backup database y to '10.bak'; ERROR 2013 (HY000): Lost connection to MySQL server during query