Re: SQLException: innodb_log_file_size headache

Am 21.03.2016 um 10:07 schrieb Jonathan Feally:
> After taking a look in lmtp logs I found:
> Mar 21 01:28:57 mail.consult-sc dbmail-lmtpd[74282]: [0x804c21810]
> Error:[message] blob_insert(+203): SQLException: The size of BLOB/TEXT
> data inserted in one transaction is greater than 10% of redo log size.
> Increase the redo log size using innodb_log_file_size

that's a change in MySQL 5.6 / MariaDB 10.0.x

remember you can't change "innodb_log_file_size" without shutdown the 
server and delete the currect "ib_logfile0" and "ib_logfile1" because 
otherwise mysqld won't start again

> Here is a link to explain what changed in MySQL:
> http://dba.stackexchange.com/questions/75328/row-size-error-with-mysql
>
> This message is to make sure that nobody else starts to run into this
> issue.
>
> My change to my.cnf:
> ###innodb_log_file_size=5242880 # Too Small!!
> innodb_log_file_size=1048576000 # Close to 100MB accepted now which is
> large enough for most normal email setups

mysql:
innodb_log_file_size = 512M

postfix:
message_size_limit = 26214400

dbmail:
max_message_size = 26214400

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlbvz34ACgkQhmBjz394Ann4xwCfTDUfiz35G3W0+E9YkbqzbuFB
Z2YAnjuJHpmnaPI6kA+gHx0QKVZcU/ET
=59wQ
-----END PGP SIGNATURE-----