Widenius: Bug Ridden MySQL 5.1 GA Released

By Marc Handelman on December 1st, 2008

Michael Widenius, founder and original developer of MySQL (now a unit of Sun Microsystems, Inc. NasdaqGS: JAVA), has posted a long list of bugs, (some show stoppers) resident within the recently released MySQL 5.1. Essentially, in our opinion and without rancor, the release of crufty code, and the assumption of users acting as quality assurance resources is indicative of a flawed development process. More information appears after the jump.

From the Widenius post: “Some examples of older bugs that *should* have been fixed in 5.1 before GA:

Bug #989 “If DROP TABLE while there’s an active transaction, wrong binlog order”. This is a bug that has been known since August 2003, and has been discussed an referred to in several public places, including Wikipedia and my last talk at the MySQL users conference. It allows in effect anyone with rights to any database that is replicated to take down all slaves (either by accident or intentionally). This is also a bug that has been hit by several of our users in the past.
Bug #33082 Stored Procedure: crash if table replaced with a view in a loop
Bug #33094 Error in upgrading from 5.0 to 5.1 when table contains triggers
Bug #34110 Crash in InnoDB when used “embedded”
Bug #34502 mysqladmin debug causes a crash when server is creating/dropping many tmp tables
Bug #34660 crash when federated table loses connection during insert … select
Bug #37756 enabling fulltext indexes with MyISAM_repair_threads > 1 causes crash
Bug #37936 “Crash when executing a query containing date expressions”
Bug #38816 kill + flush tables with read lock + stored procedures causes crashes!
Bug #39178 Server crash in YaSSL with non-RSA-requesting client if server uses RSA key
Bug #40386 Not flushing query cache after truncate
Bug #40675 MySQL 5.1 crash with index merge algorithm and Merge tables
Bug #32868 Stored routines do not detect changes in meta-data. Note that this will not be fixed until 6.1 !
Bug #39526 sql_mode not retained in binary log for CREATE PROCEDURE
The federated engine is not enabled by default. It was disabled during a previous MySQL-5.1 “RC” release because of bugs filed against the Federated engine that MySQL developers didn’t have time to fix. This solution was deemed to be easier than upgrading the Federated engine to a newer version of the engine. This means that people that have problems with the federated engine are better off using a FederatedX plugin, compiling MySQL them self together with FederatedX or use the ourdelta MySQL distribution which contains FederatedX.
MySQL-Cluster bugs are not fixed in MySQL 5.1; Instead the Cluster engine is moved from the MySQL 5.1 release to a separate MySQL-Cluster release.”