Bug #75541 | mysqldump error message line number is wrong by 1 | ||
---|---|---|---|
Submitted: | 17 Jan 2015 21:16 | Modified: | 19 Jan 2015 5:19 |
Reporter: | Oli Sennhauser | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
Version: | 5.6.21, 5.6.22, 5.7.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | max_allowed_packet, mysqldump |
[17 Jan 2015 21:16]
Oli Sennhauser
[19 Jan 2015 5:19]
MySQL Verification Team
Hello Oli Sennhauser, Thank you for the report and test case. Thanks, Umesh
[19 Jan 2015 5:21]
MySQL Verification Team
//used max_allowed_packet directly with mysqldump client instead of using it from global vars or client section of my.cnf to see it // 5.7.6 [ushastry@ushastry]/export/umesh/mysql-5.7.6: bin/mysqldump -u root -p test -S /tmp/mysql_ushastry.sock --max-allowed-packet=1000000 > h.sql Enter password: mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping table `test` at row: 2 // 5.6.22 [ushastry@ushastry]/export/umesh/mysql-5.6.24: bin/mysqldump -u root -p test -S /tmp/mysql_ushastry.sock --max-allowed-packet=1000000 > h.sql Enter password: mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping table `test` at row: 2