← Back to team overview

maria-discuss team mailing list archive

Re: upgrading from mariadb 5.5.31 to mariadb 5.5.32 with innodb engine


On 7/18/2013 2:36 PM, Gabriel Sosa wrote:

few days ago we realized we got cached by the bug MDEV-4754 [1] . Today mariadb 5.5.32 has been released but among the notable Information the mysql bug #69623 [2] is mentioned in case you have the table using the Innodb engine.

per our information:

| innodb_data_file_path    | ibdata1:100M:autoextend   |

The MySQL bug 69623 refers to having two or more tablespaces. You only have one.
If you had more it would look like:
innodb_data_file_path    | ibdata1:100M;ibdata2:100M:autoextend

Also, as noted in the Release Notes, if you are using XtraDB, the default, you are not affected. If you load the innodb_plugin, you still wouldn't be in your setup, but others may be.


Follow ups