[rt-users] Got a packet bigger than 'max_allowed_packet'

[Peter Ziobrzynski]

oops, I was quoting from 4.0.0alpha manual on my disk. I went to 
internet 
http://www.mysql.com/documentation/mysql/bychapter/manual_MySQL_Database_Administration.html#MySQL_Database_Administration 
updated copy and see 1G as the limit. Here is the quote:

|max_allowed_packet| The maximum size of one packet. The message buffer 
is initialised to |net_buffer_length| bytes, but can grow up to 
|max_allowed_packet| bytes when needed. This value by default is small, 
to catch big (possibly wrong) packets. You must increase this value if 
you are using big |BLOB| columns. It should be as big as the biggest 
|BLOB| you want to use. The protocol limits for |max_allowed_packet| is 
16M in MySQL 3.23 and 1G in MySQL 4.0.



Peter Ziobrzynski wrote:

> ||Here is a quote from 4.x mysql manual:
>
> max_allowed_packet||
>    The maximum size of one packet. The message buffer is initialized to
>    |net_buffer_length| bytes, but can grow up to |max_allowed_packet|
>    bytes when needed. This value by default is small, to catch big
>    (possibly wrong) packets. You must increase this value if you are
>    using big |BLOB| columns. It should be as big as the biggest |BLOB|
>    you want to use. The current protocol limits |max_allowed_packet| to
>    16M.
>
>
> Sebastian Flothow wrote:
>
>> Am Donnerstag den, 12. Juni 2003, um 12:56, schrieb Marcus Ramberg:
>>
>>> Does this mean that 16M is the biggest record mysql can handle?
>>
>>
>>
>> With MySQL 3.23, yes. MySQL 4 can handle up to 2G, though I don't 
>> know what DBD::mysql supports.
>>
>>
>> Sebastian
>>
>> -- 
>> Sebastian Flothow
>> sebastian at flothow.de
>>
>> > Because it reverses the logical flow of conversation.
>> Why is top posting frowned upon?
>>
>> _______________________________________________
>> rt-users mailing list
>> rt-users at lists.fsck.com
>> http://lists.fsck.com/mailman/listinfo/rt-users
>>
>> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
>>
>
>


-- 
Peter Ziobrzynski, mailto:pzi at pzi.net