> > * If you want to do it this very moment, read the instructions at > > http://www.mysql.com/doc/I/n/Installing_source_tree.html and install a > > pre-release 4.0.2 MySQL on your test server. You may also wait until 4.0.2 is > > released, but in that case, replication in 4.0.2 may have a bug you could > > have caught on your system and it will not be fixed until 4.0.3. > > Is that possible to provide a binary snapshot of the pre-release? > This can be done with some simple shell scripting, I think. > I always found the one I build myself is about 30-50% slower > then the official binary. I think that's related to the debian patched > glibc-2.95 I am using.
Hi, I have to agree with this. I don't want to have to factor in RedHat's 7.2 compiler oddities (which one to use?). Some software projects have a machine to do regular builds on a schedule. This would be ideal. You would find more people testing it. You might just do it in special cases like this one. > Testing the new code is relatively easy, and does not require risking the > stability of your application by running alpha code. Yes and no. Taking down a server and copying gigs of data can take down a service for a long time (moving gigs of data just is never fast, and the machine I'm going to use has lots of power but no RAID). I don't have time to download and install gcc, bitkeeper, autoconf 2.13, automake 1.4, libtool, m4, and mysql today, but I'll try and get to it this week. Taking down the server will have to wait until maintenance windows over the weekend anyhow. Our test plan for MySQL 4 is as follows: 1. Serialized writes (i.e. replication slave) for two weeks (or about 1 billion insert/update/delete type queries) with no crashes. 2. Everything. We will have the app send duplicates of all queries to the mysql 4 server, but will automatically halt when mysql 4 crashes. We will keep trying this until mysql doesn't crash for a week. 3. Check that the two servers hold the same information and return the same results from queries. With the type and volume of queries that we have, mysql alpha versions either fail within minutes/hours/days or they don't fail at all. We certainly are not the biggest user of mysql, but historically, we have been able to push it hard enough to crash. Not the stable version though. Thankfully, that takes a licking and keeps on ticking. :) Eventually (spring/summer), we will move the main server to v4 and keep the slave around as a live backup. I've been wanting such a slave for a long time. Stopping the slave to make a backup would be great. Not to mention faster fulltext and order by DESC. Sincerely, Steven Roussey http://Network54.com/?pp=e --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
