MySQL InnoDB crash

Posted on Wednesday 28 May 2008, at 18:00 UTC

Well, we managed to corrupt the InnoDB MySQL storage engine files while cleaning user databases.We set up in production the backup of the last night.

By the way, this is normally not our job to clean the spams in your databases, but we have to do that because we cannot afford the load of billions of spams, so if you don't want that we need to handle the files used by MySQL or PostgreSQL, clean them. In our opinion, this is the time to think to switch to something that don't break, switch to PostgreSQL.

Edit: Well, we had to restore from databases dumps this night in order to fix the corrupted InnoDB database. The records of yesterday are of course lost, but the coherency is assured, which is the most important thing. Everything is good for now.