2

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?

4
  • By any chance, are you using InnoDB with BLOB/TEXT data ??? Dec 22, 2011 at 19:48
  • Yes, it's LONGTEXT column into which the data is inserted
    – Confusion
    Dec 24, 2011 at 9:57
  • Are you using InnoDB ? Dec 24, 2011 at 12:01
  • Sorry, I forgot to answer that: InnoDB is the only engine I've ever used for production purposes
    – Confusion
    Dec 24, 2011 at 13:01

1 Answer 1

2

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.

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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