dblog fails to log INNODB_LOG_FILE_SIZE errors

Created on 5 December 2016, over 8 years ago
Updated 5 March 2025, 29 days ago

Problem/Motivation

If a big string is inserted into a MySQL / Maria DB BLOB field that exceeds 10% of the the innodb_log_file_size setting you get this error message:

The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size.

Like in #972528: dblog fails to log MAX_ALLOWED_PACKET errors because they're longer than MAX_ALLOWED_PACKET the complete error message contains the complete query itself that caused the error. Therefore it is impossible to succeed to log that exception in a MySQL dblog.

Proposed resolution

Like in #972528: dblog fails to log MAX_ALLOWED_PACKET errors because they're longer than MAX_ALLOWED_PACKET the error message needs to be truncated before written to dblog.

Remaining tasks

none

User interface changes

none

API changes

none

Data model changes

none

🐛 Bug report
Status

Needs work

Version

11.0 🔥

Component

mysql db driver

Created by

🇩🇪Germany mkalkbrenner 🇩🇪

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024