Mysql 4.1.18 is out with huge performance bug fix

Unread post by **scott** » Thu Mar 16, 2006 9:24 am

excellent, I'll probably get 4.1.18 into [atomic] today or tomorrow

Brent · Unread post by **Brent** » Tue Mar 21, 2006 12:53 am

Test version works for me

WarForge00 · Unread post by **WarForge00** » Mon Mar 27, 2006 12:18 pm

Still showing MySQL 4.1.15 in production. When's .18 going to move over?

Unread post by **scott** » Wed Mar 29, 2006 8:32 am

Its going out right now. Should be synced into the archives in a few hours

Snapdragon · Unread post by **Snapdragon** » Fri Apr 14, 2006 11:04 pm

I went ahead and upgraded to 18 tonight. Will let you know of any issues.
Currently doing 27 queries per second.

When I run PMA though it says MySQL 18 but client is still 15.. is that right?

Snapdragon · Unread post by **Snapdragon** » Sat Apr 15, 2006 3:12 am

Never mind, they both say 18 now... I think the client end just wasn't restarted.

Unread post by **scott** » Sat Apr 15, 2006 11:12 am

Yep, thats generally the culprit, you'll see the same thing with php or apache. I could restart mysql from the rpm (and in fact I used to), but its considered bad form to do that in an rpm unless you absolutey have to.

Snapdragon · Unread post by **Snapdragon** » Sat Apr 15, 2006 3:59 pm

Well, Plesk must have did it during it's upgrade, so I guess they figure it's ok. Actually, I guess Plesk shuts down everything, which is really annoying since quotacheck runs and keeps the webserver offline for 5 minutes.

Guess I shouldn't complain, at least with my RAID setup, it only takes 5 minutes, some people probably take half an hour or more.