Problem Solved - AND - How to decide when to upgade a production server MySQL

[Richard S. Huntrods]

My problem with deletes/inserts corrupting the database table has been 
resolved. I was using version 4.0.15, and the very bug I experienced was 
reported for version 4.0.14. As of 4.0.17, it is fixed. Interestingly, 
the bug does not appear in 4.0.5a on my Solaris box.

Which brings me to my more "global" (a.k.a. of importance to many 
persons using MySQL) question...

When do you justify upgrading to a new version of MySQL on a production 
server?

I've been upgrading MySQL versons pretty regularly on my development 
machine. Not every time, but about every quarter (3 months). Until this 
particular bug, I've never had a big problem with the devel version 
being newer than the production version. (in this case, the bug was 
discovered during my servlet junit tests, and so prevented me from 
distributing the new code until I had resolved the problem).

However, because the current "production" version I'm using (4.0.5a on 
Solaris SPARC 2.8) is working perfectly, I am very reluctant to upgrade 
the production version unless I have a good reason to do so. The problem 
is that I'm at a loss to explain what a "good reason" might be. :-)

How do those of you using MySQL in production mode make your upgrade 
decisions? As a related question, what version would you run on a 
Solaris 2.8 (SPARC) server?

Cheers,

-Richard



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]