Xaprb

Stay curious!

What are your favorite MySQL bug reports?

with 9 comments

Bug reports can be fun. They can also be terrible. Either way they can be entertaining. On the Drizzle IRC channel today I saw a couple references to MySQL bug reports: it is stop working and Does not make toast (which reminds me of the Mozilla bug report about the kitchen sink). Got any other favourites1?

1 This one’s for Jay.

Written by Baron Schwartz

August 23rd, 2010 at 7:00 pm

Posted in SQL

Tagged with

9 Responses to 'What are your favorite MySQL bug reports?'

Subscribe to comments with RSS

  1. #989 : It only took 7 years to resolve.

    Rob Wultsch

    23 Aug 10 at 8:58 pm

  2. I’m still waiting for Bug#2 (Does not make toast) to be fixed! In all seriousness, there’s a back story for Bug#2, Jim Winstead asked me to file a bug that could be used to check some various workflows, but that would obviously not be real. “Does not make toast” was what I could come up with in the shortest amount of time.

    I suppose I could’ve been all emacs-focused and asked for mysql to be able to read my NNTP feed, or my e-mail, but someone might have taken *that* seriously.

    Mark Matthews

    23 Aug 10 at 9:37 pm

  3. It would be nice if we could vote for bugs like we could with bugzilla.

    Daniël van Eeden

    24 Aug 10 at 2:50 am

  4. #989
    yeah, got resolved in the trunk (5.5.3-m3 and above) so the fix isn’t available for the stable/GA branches AFAIK

    Tyrael

    Tyrael

    24 Aug 10 at 3:08 am

  5. More background.

    Bug #56177 “it is stop working”, was initially filed as a security vulnerability (!!), which indicates that the reporter is either clueless or a troll.
    My initial reaction was to mark it as “closed” with a comment: “Fixed. Method used: see ‘how to repeat’”.
    But then I remembered the advice about not feeding the trolls …

    Giuseppe Maxia

    24 Aug 10 at 3:10 am

  6. You should open up the definition to MySQL+friends ;) This one is just too funny:

    http://bugs.php.net/52435

    Morgan Tocker

    24 Aug 10 at 3:38 am

  7. Funny bugs are…well funny! :) But there are a lot of interesting serious bugs:

    #1341 “InnoDB ibdata1 never shrinks after data is removed.” Which is mostly fixed in 5.5 by changing the innodb_file_per_table default value.

    #34037 “ipv6-capable inet_aton and inet_ntoa functions needed” This is just part of the missing IPv6 support in MySQL. IPv6 was on the list for MySQL 6.0 (See also: WL#798)

    #53336 “Improved InnoDB Transaction Reporting” Just shows that good contributions are still happening :)

    Daniël van Eeden

    24 Aug 10 at 3:57 am

  8. Of my own reported bugs:
    #20924 “CAST(expr as UNSIGNED) returns SIGNED value when used in various functions” Old 1/2 fixed bug from before I joined MySQL 4yrs ago.
    #31484 “Cluster LOST_EVENTS entry not added to binlog on mysqld restart.” Old favorite, silent replication breakage from restarting Cluster SQL node.
    #55641 “Stopping node gracefully in the master cluster can create an inconsistent slave” New favorite, silent replication breakage from restarting Cluster NDBD node.

    All time funniest/scariest bug was:
    #40854 “SHOW TABLES removes tables from Cluster” *cringe*

  9. Bug 40854 was a doozie, yeah.

    Xaprb

    25 Aug 10 at 2:16 pm

Leave a Reply