We're updating the issue view to help you get more done.Learn more

InnoDB Logfile size - misleading error message

It may happen, that an insert statement fails, because of an insufficient size of the InnoDB logfile, eg. described here:
http://stackoverflow.com/questions/25299370/mysql-error-1118-row-size-too-large-when-restoring-django-mailer-database

The problem is, that the logfile is to small to handle the insert bundled insert statment used by the created dumpfile (one insert, multiple rows). This may lead to an undesired case where you may create a dump, but you are not able to restore the dump on the same sever.

The error message given ist Error 1118 (Row size too large) - which is misleading at best, in case of an overrun in the logfile, the error should reflect this and give a correct hint to the user.

Status

Assignee

Jan Lindström

Reporter

Kai Schlachter

Sprint

None

Fix versions

Affects versions

10.0

Priority

Minor