How to upgrade to MySQL 5.0

[Ron Rudman]

I'd like to upgrade my MySQL 4.14 to 5.0. Can I just "do it" (following the standard upgrade instructions from MySQL.com) without winding up with a "misconfigured Plesk"?

 

[atomicturtle]

Ive got Mysql 5.0.x packages in my archive, which you can access through yum.

1) add the archive / fix yum if you're on a VPS
wget -q -O - http://www.atomicorp.com/installers/atomic |sh

2) upgrade
yum update

Thats it!

 

[Ron Rudman]

My host doesn't have yum, but I wound up putting MySQL 5.1 out there - ready to instal. Your reply makes it seem that I just do this upgrade, but I want to be sure which of several possible paths to follow so Plesk continues to function normally. I know there are *some* restrictions, because the PLESK startup script S85psa assumes there's a mysql user named "admin", that the socket is in "var/lib", etc. But it also uses a variable $MYSQL_BIN_D, which suggests that MySQL can in fact be anywhere. So specifically, which path should I take:

Path 1: Install on top of the existing MySQL (/usr) and upgrade the psa database.
Path 2: Install in a completely separate place (/usr/local) and let PLESK continue to use the version it's using - tempting, but they can't both use port 3306.

 

[atomicturtle]

All this works with plesk just fine (I'm a founder of plesk, it'd better!).

When you're working with rpm managed files, you always have the option of rolling back the update, either through the internal rollback system, or by passing in the --oldpackage flag on an "update".

The mysql rpms from all vendors (centos, redhat, fedora) do not touch, or otherwise modify an existing installation on an update event.

 

[Ron Rudman]

Great! Thanks very much for the support.