MySQL Server 5.1.30 has been released

Woehoe, it's official now!

Dear MySQL users,

We are proud to present to you the MySQL Server 5.1.30 GA release, the
first 5.1 production version of the popular open source database.
MySQL 5.1.30 is recommended for use on production systems.

MySQL 5.1 provides a number of new enhancements including:

- Table and index partitioning
- Row-based and mixed replication
- Built-in job scheduler
- Improved XML handling with XPath support
- New SQL diagnostic aids and performance utilities
- The return of the embedded library (libmysqld)

For a more complete look at what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.30 on new servers or upgrading
to MySQL 5.1.30 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if
you can't find this version on some mirror, please try again later or
choose another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc.:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-30.html

Sincerely,

Kent Boortz
The MySQL build team at Sun Microsystems

=======================================================================

Bugs fixed:

* Partitioning: A SELECT using a range WHERE condition with an
ORDER BY on a partitioned table caused a server crash.
(Bug#40494: http://bugs.mysql.com/40494)

* Partitioning: Dropping or creating an index on a partitioned
table managed by the InnoDB Plugin locked the table.
(Bug#37453: http://bugs.mysql.com/37453)

* Replication: Row-based replication failed with non-partitioned
MyISAM tables having no indexes.
(Bug#40004: http://bugs.mysql.com/40004)

* With statement-based binary logging format and a transaction
isolation level of READ COMMITTED or stricter, InnoDB printed
an error because statement-based logging might lead to
inconsistency between master and slave databases. However,
this error was printed even when binary logging was not
enabled (in which case, no such inconsistency can occur).
(Bug#40360: http://bugs.mysql.com/40360)

* The CHECK TABLE ... FOR UPGRADE statement did not check for
incompatible collation changes made in MySQL 5.1.24. (This
also affects mysqlcheck and mysql_upgrade, which cause that
statement to be executed.)
Prior to this fix, a binary upgrade (performed without dumping
tables with mysqldump before the upgrade and reloading the
dump file after the upgrade) would corrupt tables. After the
fix, CHECK TABLE ... FOR UPGRADE properly detects the problem
and upgrades tables.
However, the fix is not backward compatible and can result in
a downgrading problem under these circumstances:

1. Perform a binary upgrade to a version of MySQL that
includes the fix.

2. Run CHECK TABLE ... FOR UPGRADE (or mysqlcheck or
mysql_upgrade) to upgrade tables.

3. Perform a binary downgrade to a version of MySQL that
does not include the fix.

The solution is to dump tables with mysqldump before the
downgrade and reload the dump file after the downgrade.
Alternatively, drop and recreate affected indexes.
(Bug#40053: http://bugs.mysql.com/40053)

* Some recent releases for Solaris 10 were built on Solaris 10
U5, which included a new version of libnsl.so that does not
work on U4 or earlier. To correct this, Solaris 10 builds now
are created on machines that do not have that upgraded
libnsl.so, so that they will work on Solaris 10 installations
both with and without the upgraded libnsl.so.
(Bug#39074: http://bugs.mysql.com/39074)

* XA transaction rollbacks could result in corrupted transaction
states and a server crash.
(Bug#28323: http://bugs.mysql.com/28323)

* ALTER TABLE for an ENUM column could change column values.
(Bug#23113: http://bugs.mysql.com/23113)

how upgrade！

I do not feel very confident to upgrade MySQL with existing DA on the server. I will prefer to wait until an official upgrade is available trough custombuild...

5.0 seems like its only been out 5 minutes. Generally I dont reccomend jumping onto early releases as bugs are likely to surface when mass adoption is in early stages.

I read this article (in Swedish though), where MySQL's main developer, Michael Widenius, says that "Sun has no quality control" and where Widenius also says that there was over 180 critical bugs in 5.1 at the time of it's release.

Thus, it might be a good idea to not upgrade instantly.

Installation for RedHat based systems (Fedora, CentOS, RedHat, RHEL):

Henrik said:

I read this article (in Swedish though), where MySQL's main developer, Michael Widenius, says that "Sun has no quality control" and where Widenius also says that there was over 180 critical bugs in 5.1 at the time of it's release.

Click to expand...

And for those who don't read Swedish, a post in Monty's own blog: "Oops, we did it again (MySQL 5.1 released as GA with crashing bugs". Interesting post and interesting comments.

I especially love the well documented Bug #989, which has been there since August 2003 and still not fixed (It allows in effect anyone with rights to any database that is replicated to take down all slaves - either by accident or intentionally).

Then again, Monty says that if you're not using any of the new 5.1 features, 5.1 is "more stable 5.0 than 5.0 was".

Henrik said:

Thus, it might be a good idea to not upgrade instantly.

Click to expand...

Well, I know I'll be waiting for a bit with this one.

Actually, if you read Monte's blog-post carefully you'll see that the bugs are worse in 5.0. They're not generally affecting what we do with MySQL. He recommends updating to 5.1 if you're already using 5.0. Read the entire blog post.

Jeff

smtalk said:

Installation for RedHat based systems (Fedora, CentOS, RedHat, RHEL):

Code:

cd /usr/local/directadmin/custombuild/mysql
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-server-5.1.30-0.glibc23.i386.rpm/from/http://mysql.mirror.kangaroot.net/
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-client-5.1.30-0.glibc23.i386.rpm/from/http://mysql.skynet.be/
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-devel-5.1.30-0.glibc23.i386.rpm/from/http://mysql.mirror.kangaroot.net/
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-shared-5.1.30-0.glibc23.i386.rpm/from/http://mysql.skynet.be/
cd ..
perl -pi -e 's/5.1.23-rc/5.1.30/' versions.txt
perl -pi -e 's/mysql=5.0/mysql=5.1/' options.conf
perl -pi -e 's/mysql_backup=no/mysql_backup=yes/' options.conf
perl -pi -e 's#MySQL-client-\${MYSQL_VER}-0.i386.rpm#MySQL-client-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MySQL-devel-\${MYSQL_VER}-0.i386.rpm#MySQL-devel-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.i386.rpm#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MySQL-shared-\${MYSQL_VER}-0.i386.rpm#MySQL-shared-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
./build mysql

If phpMyAdmin has any problems:

Code:

perl -pi -e "s#'mysqli'#'mysql'#" /var/www/html/phpMyAdmin/config.inc.php

Click to expand...

it required me to install perl-DBI first but updated fine. thanks

smtalk said:

Installation for RedHat based systems (Fedora, CentOS, RedHat, RHEL):

Code:

cd /usr/local/directadmin/custombuild/mysql
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-server-5.1.30-0.glibc23.i386.rpm/from/http://mysql.mirror.kangaroot.net/
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-client-5.1.30-0.glibc23.i386.rpm/from/http://mysql.skynet.be/
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-devel-5.1.30-0.glibc23.i386.rpm/from/http://mysql.mirror.kangaroot.net/
wget http://dev.mysql.com/get/Downloads/MySQL-5.1/MySQL-shared-5.1.30-0.glibc23.i386.rpm/from/http://mysql.skynet.be/
cd ..
perl -pi -e 's/5.1.23-rc/5.1.30/' versions.txt
perl -pi -e 's/mysql=5.0/mysql=5.1/' options.conf
perl -pi -e 's/mysql_backup=no/mysql_backup=yes/' options.conf
perl -pi -e 's#MySQL-client-\${MYSQL_VER}-0.i386.rpm#MySQL-client-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MySQL-devel-\${MYSQL_VER}-0.i386.rpm#MySQL-devel-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.i386.rpm#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MySQL-shared-\${MYSQL_VER}-0.i386.rpm#MySQL-shared-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
./build mysql

If phpMyAdmin has any problems:

Code:

perl -pi -e "s#'mysqli'#'mysql'#" /var/www/html/phpMyAdmin/config.inc.php

Click to expand...

get error follow :

[root@host custombuild]# perl -pi -e 's/5.1.23-rc/5.1.30/' versions.txt
[root@host custombuild]# perl -pi -e 's/mysql=5.0/mysql=5.1/' options.conf
[root@host custombuild]# perl -pi -e 's/mysql_backup=no/mysql_backup=yes/' options.conf
[root@host custombuild]# perl -pi -e 's#MySQL-client-\${MYSQL_VER}-0.i386.rpm#MySQL-client-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
[root@host custombuild]# perl -pi -e 's#MySQL-devel-\${MYSQL_VER}-0.i386.rpm#MySQL-devel-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
[root@host custombuild]# perl -pi -e 's#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.i386.rpm#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
[root@host custombuild]# perl -pi -e 's#MySQL-shared-\${MYSQL_VER}-0.i386.rpm#MySQL-shared-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
[root@host custombuild]# ./build mysql
Dumping database aaaa
Dumping database da_atmail
Dumping database da_roundcube
...............

--04:17:16-- http://files.directadmin.com/services/all/mysql/MySQL-client-5.1.23-rc-0.glibc23.i386.rpm
Resolving files.directadmin.com... 72.35.85.222
Connecting to files.directadmin.com|72.35.85.222|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
04:17:16 ERROR 404: Not Found.

--04:17:16-- http://files.directadmin.com/services/all/mysql/MySQL-devel-5.1.23-rc-0.glibc23.i386.rpm
Resolving files.directadmin.com... 72.35.85.222
Connecting to files.directadmin.com|72.35.85.222|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
04:17:22 ERROR 404: Not Found.

--04:17:22-- http://files.directadmin.com/services/all/mysql/MySQL-server-5.1.23-rc-0.glibc23.i386.rpm
Resolving files.directadmin.com... 72.35.85.222
Connecting to files.directadmin.com|72.35.85.222|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
04:17:22 ERROR 404: Not Found.

--04:17:22-- http://files.directadmin.com/services/all/mysql/MySQL-shared-5.1.23-rc-0.glibc23.i386.rpm
Resolving files.directadmin.com... 72.35.85.222
Connecting to files.directadmin.com|72.35.85.222|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
04:17:23 ERROR 404: Not Found.

*** Cannot find /usr/local/directadmin/custombuild/mysql/MySQL-client-5.1.23-rc-0.glibc23.i386.rpm. Aborting ***
[root@host custombuild]#

Click to expand...

Dauser2007 said:

get error follow :

Click to expand...

change autover=yes to autover=no

thanks roly !

done !

It's now included into the CustomBuild script. Happy using!

jlasman said:

Read the entire blog post.

Click to expand...

I did, and I read all the comments too.

jlasman said:

Actually, if you read Monte's blog-post carefully you'll see that the bugs are worse in 5.0. They're not generally affecting what we do with MySQL. He recommends updating to 5.1 if you're already using 5.0.

Click to expand...

Sorry, my post wasn't very clear (lack of caffeine?), but the above was basically what the "5.1 being more stable 5.0 than 5.0 was" in my post was all about.

One thing I've learned, doing this Interweb malarkey professionally for 12 years, is NOT to be the first one to "test" a new version. Waiting a bit, unless upgrade is critically needed, usually pays off. Just look at the PHP issue just the other day. That's basically what I was referring with my "I'll wait a bit" comment.

(Sorry for taking this thread a bit OT...)

I tried to use the custombuild method to update but got the following error:

Has anyone else encountered this yet and, if so, how did they proceed?

A MySQL server package (MySQL-server-4.1.10a-0) is installed.

Upgrading directly from MySQL 4.1 to MySQL 5.0 may not
be safe in all cases. A manual dump and restore using mysqldump is
recommended. It is important to review the MySQL manual's Upgrading
section for version-specific incompatibilities.

A manual upgrade is required.

- Ensure that you have a complete, working backup of your data and my.cnf
files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages. Usually this command will
list the packages you should remove:
rpm -qa | grep -i '^mysql-'

You may choose to use 'rpm --nodeps -ev <package-name>' to remove
the package which contains the mysqlclient shared library. The
library will be reinstalled by the MySQL-shared-compat package.
- Install the new MySQL packages supplied by MySQL AB
- Ensure that the MySQL server is started
- Run the 'mysql_upgrade' program

This is a brief description of the upgrade process. Important details
can be found in the MySQL manual, in the Upgrading section.
******************************************************************
error: %pre(MySQL-server-5.0.67-0.i386) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping MySQL-server-5.0.67-0
Giving mysqld a few seconds to start up...
This script updates all the mysql privilege tables to be usable by
MySQL 4.0 and above.

This is needed if you want to use the new GRANT functions,
CREATE AGGREGATE FUNCTION, or the more secure passwords in 4.1

And try again

Thank you, I had tried that but it reported it wasn't installed. Looking at the directadmin interface, I ran the same command referencing that version and that's got me a little further along.

The DirectAdmin interface reports v5.1.30, but when I launch phpMyAdmin I get the following error.

Your PHP MySQL library version 5.1.30 differs from your MySQL server version 5.0.67

I'm wondering if I accidentally partly installed MySQL first time round, before the new version had been added to custombuild which is causing the current problem.

./build versions seems to report that mysql is up-to-date.

**UPDATE: I had rebuilt ./build php n already, but I found the solution here:

http://www.directadmin.com/forum/showthread.php?t=28863

Once I'd done that and another build of php, it all now appears to be working fine. Thanks for all the help and quick suggestions.

cd /usr/local/directadmin/custombuild/mysql
wget http://dev.mysql.com/get/Downloads/...6.rpm/from/http://mysql.mirror.kangaroot.net/
wget http://dev.mysql.com/get/Downloads/...glibc23.i386.rpm/from/http://mysql.skynet.be/
wget http://dev.mysql.com/get/Downloads/...6.rpm/from/http://mysql.mirror.kangaroot.net/
wget http://dev.mysql.com/get/Downloads/...glibc23.i386.rpm/from/http://mysql.skynet.be/
cd ..
perl -pi -e 's/5.1.23-rc/5.1.30/' versions.txt
perl -pi -e 's/mysql=5.0/mysql=5.1/' options.conf
perl -pi -e 's/mysql_backup=no/mysql_backup=yes/' options.conf
perl -pi -e 's#MySQL-client-\${MYSQL_VER}-0.i386.rpm#MySQL-client-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MySQL-devel-\${MYSQL_VER}-0.i386.rpm#MySQL-devel-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.i386.rpm#MYSQLSERVER=MySQL-server-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
perl -pi -e 's#MySQL-shared-\${MYSQL_VER}-0.i386.rpm#MySQL-shared-\${MYSQL_VER}-0.glibc23.i386.rpm#' build
./build mysql

Click to expand...

what is wrong here !!!
You can not install MySQL, because you do not have it set in options.conf file.

Is mysql_inst=yes in options.conf?

accualy i have this only


#Possible values - 4.1, 5.0 or 5.1
mysql=5.1
mysql_inst=no
mysql_backup=yes

i will change it to yes

thanks a lot