MySQL Bugs: #53599: Fail on Export to Disk Operation when dump large tables

Bug #53599	Fail on Export to Disk Operation when dump large tables
Submitted:	12 May 2010 13:21	Modified:	3 Jun 2010 16:44
Reporter:	Bruno Costa	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2 OSS	OS:	Windows
Assigned to:	Alexander Musienko	CPU Architecture:	Any

Description:
When i create a dump from large tables the operation fails indicating the following error:
mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping table 'xxx' at row: 1

How to repeat:
Create a table with rows bigger than 'max_allowed_packet' and try Export this table to disk.

Suggested fix:
Put on Advance Export Options the parameter max_allowed_packet.

I contour this problem creating a batch file "mysqldump.bat" below:

"%path to mysql dump%\mysqldump.exe" %* --max_allowed_packet=268435456

and in Workbench Preferences->Administrator Tab set "Path to mysqldump Toll" to mysqldump.bat

Many thanks for writing a bug report.

You need to configure max-allowed-package under mysqldump section in my.cnf.

Unfortunately, it is not possible yet to do it with Workbench Administrator.

This is a bug in my eyes.

An option for max_allowed_packet_size should be added to Export Options tab and the default value should be set to 1G

fix confirmed in repository. 
new option added on "Advanced Export Options" Tab in Data Dump Section:
"The maximum size of one packet or any generated/intermediate string" (default value "1G")

An entry has been added to the 5.2.22 changelog:

In the Data Dump section of the Administrator, when an export was generated the following error occurred:

mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping
table 'xxx' at row: 1

This only happened for larger tables.