-
Notifications
You must be signed in to change notification settings - Fork 8.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undolog Packet for query is too large when table longblob field more than 40MB #6451
Comments
From what I see, the issue described is a solution. The default value for max_allowed_packet is 64M, yet you're describing storage of 40M, which seems to have some gap. Additionally, is the oversized transaction mentioned in the issue something encountered in a real-world scenario? |
场景:通过数据库来保存附件。 更新语句时,前置镜像 + 后置镜像 > 64MB |
Storing attachments in a database is not a good practice. It is recommended to use object storage instead. The database stores the address of the storage location. |
Ⅰ. Issue Description
Packet for query is too large (83,886,137 > 67,108,864). You can change this value on the server by setting the 'max_allowed_packet' variable.
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Minimal yet complete reproducer code (or URL to code):
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
java -version
):uname -a
):The text was updated successfully, but these errors were encountered: