Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Some time ago we started storing serialized data in our MySQL database and immediately ran into the well known 'packet too large' error. We increased max_allowed_packet to 64M and all was well.

This morning, I suddenly received a too large packet 26814732 error, even though

mysql> show variables like '%packet%';
| Variable_name      | Value    |
| max_allowed_packet | 67108864 |
1 row in set (0.00 sec)

How is this possible? I found this related post, but we are not dealing with mysqldump, we haven't changed any other database configuration settings and we've already been storing BLOBs larger than this one. What could've changed to lead to this situation?

share|improve this question
By any chance, are you using InnoDB with BLOB/TEXT data ??? – RolandoMySQLDBA Dec 22 '11 at 19:48
Yes, it's LONGTEXT column into which the data is inserted – Confusion Dec 24 '11 at 9:57
Are you using InnoDB ? – RolandoMySQLDBA Dec 24 '11 at 12:01
Sorry, I forgot to answer that: InnoDB is the only engine I've ever used for production purposes – Confusion Dec 24 '11 at 13:01
up vote 2 down vote accepted

The problem was not in fact MySQL. We use the DRb Ruby library, which gives a very similar error under similar circumstances: too large packet 26814732. Due to familiarity with the MySQL issue referenced here, I didn't read the error message well enough and didn't notice it is slightly different from Packet too Large.

share|improve this answer
+1 for solving your own problem. You can self accept/checkmark your own answer so this is at least flagged as resolved. – atxdba Feb 21 '12 at 16:08
+1 for the same reason @atxdba said... – RolandoMySQLDBA Feb 21 '12 at 16:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.