MySQL Forums
Forum List  »  Falcon

MySQL 6.0.2-alpha has been released!
Posted by: Calvin Sun
Date: September 06, 2007 02:25PM

Dear MySQL users,

The MySQL 6.0.2-alpha, a new version of the MySQL database system with the new Falcon transactional storage engine, has been released. The main page for MySQL 6.0 release is at:

For people who is new to the Falcon storage engine, please read the Falcon Evaluation Guide at:

and the Falcon White Paper at:


Falcon is currently an Alpha release and should not be used in production environments. Falcon is currently only supported within a special fork of the MySQL release, termed MySQL-6.0-falcon. This release is not considered ready for production. The mysql-6.0-falcon tree is provided only for testing and evaluation of the Falcon storage engine.

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

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.

Please also note that some of our mirrors are currently experiencing
problems that may result in serving corrupted files. We are working with
the mirror maintainers to resolve this.

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

The following section lists the changes in the Falcon storage engine since the last released version of MySQL 6.0. It can also be viewed online at

Changes since the last release:

Functionality added or changed:

* 64-bit Windows support.

* Mac OS X (Intel) support has been added. To build on Mac OS X from
the repository sources you must have the most recent versions of
bison, automake, autoconf and libtool installed.

There are known issues with the Falcon on Mac OS X build. (Bug#30564)

* Support for tablespaces.

* New performance settings, falcon_index_chill_threshold,
falcon_record_chill_threshold, and falcon_log_windows.

* The Falcon record cache parameters have been altered. The
falcon_max_record_memory and falcon_min_record_memory are no longer

Instead, falcon_record_memory_max, falcon_record_scavenge_threshold,
falcon_record_scavenge_floor and falcon_inital_allocation parameters
are now used to control the caching of records in memory within Falcon.
See Section 3.1, “Configuration Parameters”. (Bug#30083)

The option falcon_initial_allocation has been added to control the
initial size of a Falcon tablespace on disk.

The option falcon_disable_fsync has been added. If set to true, then
the periodic fsync operation is disabled.

Bugs fixed:

* Renaming tables to or from Falcon tablespaces would raise an error.

* Some Falcon variables were marked as status variables. (Bug#29169)

* Under certain situations the Falcon tables and log could become corrupt
and prevent recovery from a crashed version of the files. (Bug#28351)

* Updating a large table without an index would lock all the records
during a transaction and unlock the records individually. (Bug#30124)

* Falcon would incorrectly allow creation of two tables with the same
name but different case sensitivity, without raising an error, but
treat the two tables as the same during further queries. (Bug#30210).

* When loading large datasets into a Falcon table mysqld could crash. An
Out of memory error will now be raised in this situation. (Bug#30251)

* An assertion could be thrown during high number of concurrent updates
of BLOB fields. (Bug#30463)

* Accessing an INFORMATION_SCHEMA table generated by Falcon, when Falcon
has not been enabled would cause mysqld to crash. (Bug#29014)

* Falcon could occasionally report a problem with a duplicate key error
during INSERT when inserting the same data into a unique column on two
or more connections simultaneously. (Bug#29240)

* For debug builds, the server crashed when inserting a negated DECIMAL
value of maximum precision (65 digits), such as for INSERT INTO ...
SELECT -col_val ... (Bug#28810)

* Creating a tablespace with a unique name but using the same datafile
as an existing tablespace results in the re-initialization of the
tablespace and the loss of the data contained in it. Falcon will now
report an error if you the datafile already exists. (Bug#29511)

* DELETE statements could cause a crash when many simultaneous threads
are running. (Bug#26475)

* Using SELECT on a table that uses two INT columns with a single index
would fail to return rows that queried both columns and complex
comparison operators. (Bug#29319)

* Wide DECIMAL columns would show rounding errors during SELECT.

* Inserting into a table with a unique index simultaneously on two
connections in a way that would cause a deadlock would cause MySQL to
hang. The deadlock situation is now identified and an error will be
raised. (Bug#29206)

* Accessing data within DECIMAL columns wider than 18 digits would cause
a crash. (Bug#28725)

* Falcon would fail to build under Mac OS X/Intel. A preliminary patch is
available to allow building under Mac OS X/Intel only (PowerPC support
is not yet available). Note that Mac OS X/Intel is still an unsupported
platform. (Bug#26466)

* Under certain situations, shutting down MySQL using mysqladmin could
cause Falcon to corrupt the database tables and fail to restart
properly. (Bug#26296)

* Queries could fail with a Can't find record in ... error. (Bug#26328)

* DECIMAL columns with large widths did not work, either during INSERT or
SELECT. (Bug#26607).

* Renaming a database would raise error ERROR 1030 (HY000): Got error 157
from storage engine. (Bug#22182)

* Loading certain datasets through a direct import could cause index
problems and crash. (Bug#26930)

* Inserting large numbers of identical columns into a table, followed by
a SELECT or UPDATE could cause a hang or crash. (Bug#27277)

INFORMATION_SCHEMA would be reported incorrectly. (Bug#28197)

* Unique indexes on VARCHAR columns are not identified correctly.

* mysqld would crash after a high number of ALTER TABLE, INSERT and
UPDATEstatements. (Bug#22154, Bug#28515)

* Searching for rows within a table with some non-western character sets
would fail to return the right results if the SELECT relied on an
index. (Bug#27697)

* Searches for accented characters in a UTF8 table fail if an index
exists for the column. (Bug#26057)

* Searches using LIKE on a UTF8 table fail if the search relies an
indexed column. (Bug#24921)

* Searches for data on a partial index for a column using the UTF8
character set would fail. (Bug#24858)

* Searches for data using exotic collation/character sets fail if the
search relies on an indexed column. (Bug#23689)

* Inserting rows to a table with a unique index where the unique index
value is identical on two separate connections would block the second
transaction. (Bug#22847)

* Large inserts to a table within a single transaction trigger high
memory usage and may ultimately crash. (Bug#22169)


Options: ReplyQuote

Written By
MySQL 6.0.2-alpha has been released!
September 06, 2007 02:25PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.