Dear MySQL users,
We are proud to present to you the MySQL Server 5.1.24-rc release,
a new release candidate version of the popular open source database.
Bear in mind that this is still a candidate release, and as with any
other pre-production release, caution should be taken when installing on
production level systems or systems with critical data. For production
level systems using 5.0, we would like to direct your attention to the
product description of MySQL Enterprise at:
http://mysql.com/products/enterprise/
The MySQL 5.1.24-rc release is now available in source and binary form
for a number of platforms from our download pages at
http://dev.mysql.com/downloads/
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.:
http://forge.mysql.com/wiki/Contributing
The description of the changes from version 5.1.23-rc to this 5.1.24-rc
is some 1,800 lines long, that is about 96 kB. As some mail systems are
bound to truncate long mail at 64 kB, I split the announcement into two
parts - this is part 1 only.
The following section lists the (first part of the) changes from version
to version in the MySQL source code since the latest released version of
MySQL 5.1, the MySQL 5.1.23-rc release. It can also be viewed online at
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-24.html
Sincerely,
Kent Boortz
The MySQL build team at Sun Microsystems
==
Functionality added or changed:
* Please note that the Federated engine is not built into the MySQL
5.1.24 RC release binaries, but is scheduled to return in the next
release, which will be MySQL 5.1.25. The reasons for Federated's
omission in 5.1.24 RC includes various quality and timing issues
that unfortunately could not be avoided, and we apologize for any
inconvenience this has caused.
* Windows Installer: Important Change: The data directory now defaults
to the Windows Common App Data Folder (on Windows XP, this is
...\All Users\Application Data; on Vista, it is ProgramData).
(Bug#34593: http://bugs.mysql.com/34593)
* Cluster API: Important Change: Because
NDB_LE_MemoryUsage.page_size_kb shows memory page sizes in
bytes rather than kilobytes, it has been renamed to
page_size_bytes. The name page_size_kb is now deprecated and
thus subject to removal in a future release, although it
currently remains supported for reasons of backwards
compatibility. See The Ndb_logevent_type Type
(http://dev.mysql.com/doc/ndbapi/en/ndb-logevent-type.html),
for more information about NDB_LE_MemoryUsage.
(Bug#30271: http://bugs.mysql.com/30271)
* Replication: Introduced the slave_exec_mode system variable to
control whether idempotent or strict mode is used for
replication conflict resolution. Idempotent mode suppresses
duplicate-key, no-key-found, and some other errors, and is
needed for circular replication, multi-master replication, and
some other complex replication setups when using MySQL
Cluster. Strict mode is the default.
(Bug#31609: http://bugs.mysql.com/31609)
* Replication: When running the server with
--binlog-format=MIXED or --binlog-format=STATEMENT, a query
that referred to a system variable used the slave's value when
replayed on the slave. This meant that, if the value of a
system variable was inserted into a table, the slave differed
from the master. Now, statements that refer to a system
variable are marked as unsafe, which means that:
+ When the server is using --binlog-format=MIXED, the
row-based format is used automatically to replicate these
statements.
+ When the server is using --binlog-format=STATEMENT, these
statements produce a warning.
(Bug#31168: http://bugs.mysql.com/31168)
See also Bug#34732: http://bugs.mysql.com/34732
* The ndbd and ndb_mgmd manpages have been reclassified from
volume 1 to volume 8. (Bug#34642: http://bugs.mysql.com/34642)
* For binary .tar.gz packages, mysqld and other binaries now are
compiled with debugging symbols included to enable easier use
with a debugger. (Bug#33252: http://bugs.mysql.com/33252)
* Formerly, when the MySQL server crashed, the generated stack
dump was numeric and required external tools to properly
resolve the names of functions. This is not very helpful to
users having a limited knowledge of debugging techniques. In
addition, the generated stack trace contained only the names
of functions and was formatted differently for each platform
due to