Page 2 of 2
Posted: Thu Mar 16, 2006 9:24 am
by scott
excellent, I'll probably get 4.1.18 into [atomic] today or tomorrow
Posted: Tue Mar 21, 2006 12:53 am
by Brent
Test version works for me
Posted: Mon Mar 27, 2006 12:18 pm
by WarForge00
Still showing MySQL 4.1.15 in production. When's .18 going to move over?
Posted: Wed Mar 29, 2006 8:32 am
by scott
Its going out right now. Should be synced into the archives in a few hours
Posted: Fri Apr 14, 2006 11:04 pm
by Snapdragon
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?
Posted: Sat Apr 15, 2006 3:12 am
by Snapdragon
Never mind, they both say 18 now... I think the client end just wasn't restarted.
Posted: Sat Apr 15, 2006 11:12 am
by scott
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.
Posted: Sat Apr 15, 2006 3:59 pm
by Snapdragon
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.