Why you won't use MySQL/ndb
Par jd le dimanche, juin 17 2007, 11:25 - Free Software - Lien permanent
I just failed to migrate a big project at work because of that, the D day:
Jun 15 10:46:39 hostname mysqld[20095]: Version:'5.0.32-Debian_7etch1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution Jun 15 10:46:43 hostname mysqld[20095]: mysqld got signal 11
So no, you won't use NDB, at least with MySQL 5.0.31 (included in etch). It's _so_ buggy that we get a segfault on the first DELETE statement with a 30 MB database.
Backporting version 5.0.41 from sid gives better results (at least for now).
I knew we should have used PostgreSQL from the beginning...
Commentaires
There have been a good number of bug fixes in the gap between .31 and .41 for NDB, so .41 will no doubt end up being a lot better.
I haven't seen the bug you describe before... so perhaps it's something related to the debian package. (certainly report it to the debian BTS, debian packaging of MySQL is fairly good..).
Certainly if you can repeat it with .41, we'll get right on it... as it would certainly be a new bug.
For now I have not been able to reproduce the bug, so I keep my fingers crossed