I was planning on updating a client from Mysql 3.23 to Mysql 4.0, but
since 4.1 has stabilized I figured I'd give it a shot. And I'd also be
able to move another client off their crappy db server on the new shared
server if it had 4.1. However my setup has a few quirks.
The 3.23 install is acting for the replication master for the 4.0
install on the new server. The client is testing with 4.0 and everything
looks good. Ideally I'd like to stop replication, dump the db, upgrade
to 4.1, import the db, and start replication again. 4.1 can replicate
from 3.23, but I'm unsure if it can pick up where 4.0 left off. Has
anyone tried this? It's not the end of the world if it explodes in my
face, but I would keep up with my sleep by skipping another late night
maintenance to do a fresh dump from the master to restart replication
correctly.
The other question is about libs. I'm looking at a project that will
likely use Mysql 5.0 on the server side. At what point do I need to
update the client libs... or can I just use Mysql 4.0 libs in PHP and
whatnot till Redhat updates their builds? Some sort of checklist, Google
has been not helped so far, explaining when a client build would need to
be updated would be keen. Again not the end of the world, but I'd rather
not be building a bunch of custom packages if I can help it.
kashani
--
gentoo-user@gentoo.org mailing list
