3 messages in com.mysql.lists.bugsRe: Bug 712... Is there anybody out t...
FromSent OnAttachments
Paul Coldrey08 Jul 2003 18:13 
Sinisa Milivojevic09 Jul 2003 04:48 
Sinisa Milivojevic10 Jul 2003 05:41 
Subject:Re: Bug 712... Is there anybody out there
From:Sinisa Milivojevic (sin@mysql.com)
Date:07/09/2003 04:48:41 AM
List:com.mysql.lists.bugs

Paul Coldrey writes:

Hi Folks,

Firstly, I'm sorry to spam this list but I feel I have no option.......

I reported bug 712 which relates to the fact that 4.0.13 (and 4.1) are approximately 3x slower for inserts on indexed MyISAM tables than 3.23.49. Also, during inserts the table does not respond to selects.

I accept that the way I reported the bug didn't make it sound as major as it is - for my application, a slow database that becomes non-responsive during inserts is useless (everytime a user permission is changed my web-application disappears for 9 seconds while MySQL rebuilds a permission table). I emailed some extra information to Sergei Golubchik and Alexey Botchkov to put my point across but have heard nothing in response (and the bug is still non-critical, low priority).

I'm not trying stir up trouble, I just ask whether anyone feels this is an important bug... if so please vote. Also if anyone out there can give me permission to view the progress log for this bug that would great (I originally posted the bug the the list and Sergei added it into the database - hence I'm not the original poster).

I accept that there are many bugs, they are all important and that this one may be hard to fix. What I'd really love is some status. Because of this bug we're 3 weeks behind our launch date and I have nothing to tell my manager because noone at MySQL will talk to me. If I had some idea when a fix might appear I could at least plan some contingencies.

Cheers,

Paul

Hi!

Yes, we have processed your bug report, verified it and acknowledged it's importance.

However, a queue of important things to be done, either bugs or feature requests, is very long and it will take some time to have a developer assigned on this bug.

Solving this bug will require lot's of work, will involve a team of developers, and we are presently occupied with some more urgent matters.

Regards,