Re: Has MySQL just knowingly released a complete pile-of-shite??? - Tobias Lind - com.mysql.lists.bugs

12 messages in com.mysql.lists.bugsRe: Has MySQL just knowingly released...

From	Sent On	Attachments
Paul Coldrey	23 Jul 2003 00:27
Lenz Grimmer	23 Jul 2003 04:55	.patch
Tobias Lind	23 Jul 2003 05:34
Paul Coldrey	23 Jul 2003 06:44
Sergei Golubchik	23 Jul 2003 07:38
Jeremy Zawodny	23 Jul 2003 11:55
Cory Patterson	23 Jul 2003 12:50
Paul Coldrey	23 Jul 2003 16:06
Nick Gaugler	23 Jul 2003 23:19
Vidar	24 Jul 2003 01:20
Cory Patterson	24 Jul 2003 06:58
Sergei Golubchik	25 Jul 2003 01:27

Subject:	Re: Has MySQL just knowingly released a complete pile-of-shite???
From:	Tobias Lind (tob....@telia.com)
Date:	07/23/2003 05:34:38 AM
List:	com.mysql.lists.bugs

Hi! I just thought that I should give you my opinition on this matter. I'm running a large web site with a heavily loaded MySQL-database behind. There are contantly a lot of selects, inserts and updates hammering tables with ~30 million rows. Our prodution server is currently running MySQL 3.23.57, but we are (or should I say were) just about to launch a major update of our site. Because of the better FULLTEXT features in MySQL 4.0.x, we were planning to upgrade the db as well. It's all been running very well on our test server with 4.0.13, but we have not done any load testing.

I'm very glad that I got the information on this bug in 4.0.x, because it would most probably have caused a major performance hit on our web site. I'm NOT very glad that we will have to wait with our launch until 4.0.15 is out...

I would most definately call this bug "critical" since it (from what I understand from the description) seriously hits the performance on inserts and table locking with selects. I could easily live with slower ALERT TABLE and CREATE INDEX, but when it's affecting normal runtime performance, it's a whole different story. I really think you should reconsider your definition of "critical" in this case and quickly build a new version 4.0.14a or something like that. Because I guess it's a bit early to start asking "When will 4.0.15 be released PLEEEASE?" :)

Just my thoughts and viewpoint

----- Original Message ----- From: "Lenz Grimmer" <le...@mysql.com> Sent: Wednesday, July 23, 2003 1:55 PM Subject: Re: Has MySQL just knowingly released a complete pile-of-shite???

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi Paul,

thanks for your message.

On Wed, 23 Jul 2003, Paul Coldrey wrote:

A month ago today I sent in a bug report which showed that in most circumstances 4.0.13 runs at 1/3 of the expected speed and blocks selects on tables whilst inserts are occuring (see bug 712).

IIRC, this report came in by email and was then filed into our bug database. Thank you that you brought this to our attention!

This was assigned low priority / non-critical status....

Yes, because it did not match the criterias for what we consider a "critical bug":

- a security hole - a bug that crashes mysql - a bug that causes wrong query results

A slowdown for ALTER TABLE didn't really qualify as critical, as it's not an operation that is frequently used. Of course, it's an issue that needed to be addressed, and it has been fixed in the meanwhile.

I was surprised and so I argued for a brief time that it deserved a higher priority and then sat patiently waiting for it to be fixed. It seemed odd to me that MySQL seemed completely unperturbed that there was such a pitifully poorly performing server released as a production release. Imagine my surprise when I discovered that the bug has been fixed but was not incorporated into 4.0.14 but instead is in the change list for 4.0.15.

Yes, unfortunately the release builds were almost finished by the time this specific bug fix had been pushed into our source tree. And as there were quite a number of other critical bug fixes that needed to be put out, we decided to not restart the release builds once again to avoid further delaying of the release. A full rebuild takes quite some time, as each binary has to run through the full test suite after each build.

I remember reading somewhere (I think on your bugs site) that all bugs are fixed in the next release or noted in the documentation....

Yes, this rule applies to "critical" bugs.

I haven't checked yet, but I'm guessing the 4.0.14 documentation doesn't mention that MyISAM tables become pitifully slow for updates & inserts and block selects, if you decide to index them!

No, but we've added a note that this bug will be fixed for the 4.0.15 release.

I have been supporter of MySQL for many years and I am now feeling very sad :-(.

We apologize for this. We appreciate your feedback, but this was simply an example of bad timing.

Is 4.0.15 expected in the next couple of days or do you expect the MySQL community to put up with another sub-standard release for the obligatory month between updates?

I would not consider this release "sub-standard" or "a complete pile-of-shite", just because of this single missing bug fix. Therefore we do not intend to start with 4.0.15 right away, just to include this bug fix. Attached please find a patch that you can apply on top of the 4.0.14 source tree. Could you please give this a try and tell us, if it solves your problems?

Sorry again if we disappointed you - it was not our intention.

Bye, LenZ - -- Lenz Grimmer <le...@mysql.com> Senior Production Engineer MySQL GmbH, http://www.mysql.de/ Hamburg, Germany

For technical support contracts, visit https://order.mysql.com/?ref=mlgr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE/Hne0SVDhKrJykfIRAl1oAJ473VEr/5TyyrRpet7mpnSBtouCbgCfRcHn jxL1mF/jJtWgfKrzPP+hnbU= =j5J3 -----END PGP SIGNATURE-----

----------------------------------------------------------------------------

----