http://bugs.mysql.com/search.php seems to disagree with "This version now has zero bugs," Urlocker told eWEEK."

How could it be called a production release with this many bugs to begin with "He reported that more than 1,300 bugs (997 in 2007, 386 so far in 200 have been fixed in v5.1"

Any google search for speed comparisons with MySQL vs 'other database name here' will shine a glaring light on MySQL mis-information.

I'm the reporter on this story, thanks for your comment. I'll ask Mr. Urlocker to respond to your comment here. He is quoted accurately in the story.

Quote from Zack:
"There were zero customer reported unfixed P1 bugs in the 5.1 RC at the time I spoke with the reporter".

This is not the full truth. We have a lot of P1 bugs reported by customers in 5.1 RC, and we have had them a long time. The problem with these are that some of them have been declared to be hard to fix and have thus been moved to be fixed in 6.0, just to get out 5.1 sooner.

As an example of a bug that has been reported by several customers and which I personally think *should* be fixed in 5.1 is: http://bugs.mysql.com/bug.php?id=989.

This bug is likely to hit most high performance sites that uses replications sooner or later and it also allows anyone with full access to one replicated database, like the test database, to take down all slaves.

What Zack probably meant was P1 bugs reported by customers that we plan to fix before 5.1 is released.