I'm at work right now, helping to upgrade the MySQL master in Finance from 3.23.xx to 4.0.9. All the slaves have been running 4.0.x for a while (currently 4.0.8) so it's about time we got the master updated.

This should be interesting...

Update: So far, so good. We're actually running 4.0.8 now on the master and all slaves.

Posted by jzawodn at January 18, 2003 02:37 PM

Reader Comments
# Ed said:

If and when you have time, I'd like to hear why you upgraded, and if you ran into any particular difficulties. We might look at upgrading sometime soon at my work.


on January 18, 2003 04:01 PM
# matt said:

How's that query caching working out for you?

on January 18, 2003 05:27 PM
# Jeremy Zawodny said:

The query cache has been working well for us--for many months now.

on January 18, 2003 07:57 PM
# Simon Grabowski said:

Out of curiosity, what kernel are you running on?
We used to run on 2.4.18 (redhat-dist) kernel, but it caused many weird problems (duplicate entry errors in the logs, replication desynch, table corruption)... it all ceased when we upgraded to 2.4.20 from kernel.org

on January 19, 2003 09:05 AM
# Jeremy Zawodny said:

We're using 2.4.18 from kernel.org.

on January 19, 2003 03:00 PM
# Mohammed said:

Do you have any idea if 3.x to 5.1 would work as a direct upgrade?

on December 9, 2005 06:57 PM
Disclaimer: The opinions expressed here are mine and mine alone. My current, past, or previous employers are not responsible for what I write here, the comments left by others, or the photos I may share. If you have questions, please contact me. Also, I am not a journalist or reporter. Don't "pitch" me.


Privacy: I do not share or publish the email addresses or IP addresses of anyone posting a comment here without consent. However, I do reserve the right to remove comments that are spammy, off-topic, or otherwise unsuitable based on my comment policy. In a few cases, I may leave spammy comments but remove any URLs they contain.