Mysql 4.1.18 is out with huge performance bug fix

[Brent]

[WarForge00]

I second this one...

[scott]

Went in to the [atomic-testing] channel Feb 15th.

[WarForge00]

Any idea as to when it may be released?

[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.

[WarForge00]

I'll update the production server over the weekend and let you know the results after a week or so...

[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

[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?

[breun]

http://3es.atomicrocketturtle.com/atomi ... rt/3/RPMS/

[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.

[breun]

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.

[breun]

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?

[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.

[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.

[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...