MySQL 6.0.7 Alpha has been released

Dear MySQL users,

MySQL 6.0.7-alpha, a new version of the MySQL database system has
been released.  The main page for MySQL 6.0 release is at

  http://www.mysql.com/mysql60/

MySQL 6.0 includes two new storage engines: the transactional
Falcon engine, and the crash-safe Maria engine.

If you are new to the Falcon storage engine and need more
information, please read the Falcon Evaluation Guide at

  http://www.mysql.com/why-mysql/white-papers/falcon-gettin...

and the Falcon White Paper at

  http://www.mysql.com/why-mysql/white-papers/storage-engin...

The Maria storage engine is a crash safe version of MyISAM.  Maria
supports all of the main functionality of the MyISAM engine, but
includes recovery support (in the event of a system crash), full
logging (including CREATE, DROP, RENAME and TRUNCATE operations),
all MyISAM row formats and a new Maria specific row format.  Maria
is documented at

  http://dev.mysql.com/doc/refman/6.0/en/se-maria.html

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

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

and mirror sites.  Note that 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,
and patches at

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

The following section lists important, incompatible and security
changes since the previous version of MySQL 6.0.  The full
changelog, including many more fixes can be viewed online at

  http://dev.mysql.com/doc/refman/6.0/en/news-6-0-7.html

   Important functionality added or changed:

     * Important Change: mysqlbinlog now supports --verbose and
       --base64-output=DECODE-ROWS options to display row events as
       commented SQL statements.  (The default otherwise is to display
       row events encoded as base-64 strings using BINLOG statements.)
       See Section 4.6.7.2, "mysqlbinlog Row Event Display."
       (Bug#31455: http://bugs.mysql.com/31455)

   Important, security, or incompatible bugs fixed:

     * Security Enhancement: The server consumed excess memory while
       parsing statements with hundreds or thousands of nested
       boolean conditions (such as OR (OR ... (OR ... ))).  This could
       lead to a server crash or incorrect statement execution, or
       cause other client statements to fail due to lack of memory.
       The latter result constitutes a denial of service.
       (Bug#38296: http://bugs.mysql.com/38296)

     * Incompatible Change: There were some problems using DllMain()
       hook functions on Windows that automatically do global and
       per-thread initialization for libmysqld.dll:
          + Per-thread initialization: MySQL internally counts the
            number of active threads, which causes a delay in
            my_end() if not all threads have exited.  But there are
            threads that can be started either by Windows internally
            (often in TCP/IP scenarios) or by users.  Those threads do
            not necessarily use libmysql.dll functionality but still
            contribute to the open-thread count.  (One symptom is a
            five-second delay in times for PHP scripts to finish.)
          + Process-initialization: my_init() calls WSAStartup that
            itself loads DLLs and can lead to a deadlock in the
            Windows loader.
       To correct these problems, DLL initialization code now is not
       invoked from libmysql.dll by default.
       (Bug#37226: http://bugs.mysql.com/37226)

     * Incompatible Change: Some performance problems of SHOW ENGINE
       INNODB STATUS were reduced by removing used cells and Total
       number of lock structs in row lock hash table from the output.
       These values are now present only if UNIV_DEBUG is defined at
       MySQL build time.
       (Bug#36941: http://bugs.mysql.com/36941,
        Bug#36942: http://bugs.mysql.com/36942)

     * Important Change: The INFORMATION_SCHEMA.FALCON_TABLES table
       has been removed.
       (Bug#29211: http://bugs.mysql.com/29211,
        Bug#34705: http://bugs.mysql.com/34705,
        Bug#34706: http://bugs.mysql.com/34706)

Enjoy!

-- 
Jonathan Perkin, Product Engineering, MySQL
Database Technology Group, Sun Microsystems