Bug #45625 MySQL unable to handle rows larger than max_allowed_packet bytes
Submitted: 19 Jun 2009 18:14 Modified: 20 Jun 2009 9:28
Reporter: Kevin Benton (Candidate Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:All OS:Any
Assigned to: CPU Architecture:Any
Tags: max_allowed_packet

[19 Jun 2009 18:14] Kevin Benton 
Description:
This has long been a frustration of using MySQL - the server is unable to properly handle rows that are larger than max_allowed_packet bytes as well as rows that are larger than available RAM.  While it's not my intention to make the database a file server, it's frustrating that I can declare rows that can store much more data than the server can handle.  This has been a problem for years and really needs to be addressed so we can get large result sets back when more memory is required than is available and it needs to happen efficiently.  There is no reason I can think of that a mysqld instance should not be able to stream result sets back to a client in chunks so that the client can assemble the data it needs.  I was certain I filed this bug before, however, I don't seem to be able to find it.

How to repeat:
see description

Suggested fix:
see description
[20 Jun 2009 6:29] Sveta Smirnova 
Thank you for the reasonable feature request.
[20 Jun 2009 8:04] MySQL Verification Team 
was it bug #16356 ?
[20 Jun 2009 9:28] Sveta Smirnova 
Shane, thank you for finding this!

Closed as duplicate of bug #16356