Page 1 of 2
Mysql 4.1.18 is out with huge performance bug fix
Posted: Tue Feb 14, 2006 12:18 am
by Brent
Posted: Fri Mar 10, 2006 4:54 pm
by WarForge00
I second this one...

Posted: Fri Mar 10, 2006 5:12 pm
by scott
Went in to the [atomic-testing] channel Feb 15th.
Posted: Fri Mar 10, 2006 5:17 pm
by WarForge00
Any idea as to when it may be released?
Posted: Fri Mar 10, 2006 5:32 pm
by scott
Thats what you guys need to tell me, try it out and let me know if there are any issues. My gut feeling is that its fine, but Im the only one thats used it as far as I know.
Posted: Fri Mar 10, 2006 6:04 pm
by WarForge00
I'll update the production server over the weekend and let you know the results after a week or so...
Posted: Fri Mar 10, 2006 10:29 pm
by Snapdragon
I could install it to my production box, it would give it 2.5 million queries a day testing....

I just hate doing that.
4.1.18 changes:
http://dev.mysql.com/doc/refman/4.1/en/news-4-1-18.html
4.1.19 upcoming changes:
http://dev.mysql.com/doc/refman/4.1/en/news-4-1-19.html
I would be willing to test if somebody helps me
Posted: Sat Mar 11, 2006 3:15 pm
by hansdezwart
I have a Fedora Core 3 server with Plesk 7.5.4 running on it.
I need a version >= 4.16 MySQL installation, so I am very willing to try out the new RPM from the testing channel.
Can somebody please help me and explain what I need to add to "/etc/yum.conf" to make sure that when I run "yum update mysql" I get the correct packages?
Posted: Sat Mar 11, 2006 9:05 pm
by breun
I am affraid you overestimated me...
Posted: Tue Mar 14, 2006 12:50 pm
by hansdezwart
I am affraid this info is not quite enough for my inexperienced soul...
Can somebody please just put the actual lines that I add to yum.conf?
And the command that I run afterwards.
Re: I am affraid you overestimated me...
Posted: Tue Mar 14, 2006 12:58 pm
by breun
hansdezwart wrote:I am affraid this info is not quite enough for my inexperienced soul...
Can somebody please just put the actual lines that I add to yum.conf?
The same as for the normal atomic channel, just replace atomic with atomic-testing as you can see in the url I posted above. And then just run
yum update mysql (or
yum update if you want all testing updates). You might want to disable the testing channel afterwards if you just want to test this mysql release (add
enabled=0 to your yum entry).
If you haven't used art's mysql packages before and are installing it on a machine that already has mysql databases you will need to add 'old_passwords=1' to your [mysqld] section of /etc/my.cnf and restart mysqld.
Re: I would be willing to test if somebody helps me
Posted: Tue Mar 14, 2006 12:59 pm
by breun
hansdezwart wrote:I need a version >= 4.16 MySQL installation, so I am very willing to try out the new RPM from the testing channel.
Why do you
need >= 4.16 by the way?
Posted: Tue Mar 14, 2006 6:44 pm
by WarForge00
Reason I needed it is because of the following bug:
Character set conversion was not being done for FIND_IN_SET(). (Bug #13751)
http://bugs.mysql.com/bug.php?id=13751
I have a work around within my table / fields, but the other ppl using this version will know about it.
4.1.15 has this bug, while 4.1.16 fixes the bug.
Why I need a newer version of MySQL
Posted: Wed Mar 15, 2006 5:19 am
by hansdezwart
I use my server to run Moodle (
http://moodle.org). The requirement for the latest version is >= 4.16. I am not sure why, but I think it has to with the character encoding...
Thanks for the help. I will try it around 14:00 (NL time) today and will let you all know how it goes.
It is working!!
Posted: Wed Mar 15, 2006 10:03 am
by hansdezwart
Well I have just managed to it working on my Plesk 7.5.4 server. I do not see any immediate problems. I will let you all know when I do...