|| ||Kent Boortz <kent-AT-mysql.com>|
|| ||MySQL 4.1.18 has been released|
|| ||Tue, 07 Feb 2006 23:57:47 +0100|
|| ||mysql-AT-lists.mysql.com, packagers-AT-lists.mysql.com|
MySQL 4.1.18, a new version of the popular Open Source Database
Management System, has been released. The Community Edition 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 -
if you can't find this version on some mirror, please try again later or
choose another download site.
This is a bugfix release for the recent production version.
Please refer to our bug database at http://bugs.mysql.com/ for more
details about the individual bugs fixed in this version.
*NOTE* Due to a critical performance related bug (Bug#15935) 4.1.17
was not released. The bug was introduced within 4.1.16, we
therefore recommend all users to upgrade directly to 4.1.18
if they are using 4.1.15 or earlier.
Changes in release 4.1.18
Functionality added or changed:
* NDB Cluster: More descriptive warnings are now issued when
inappropriate logging parameters are set in config.ini. (Formerly,
the warning issued was simply Could not add logfile destination .)
* libmysqlclient now uses versioned symbols with GNU ld.
* The --replicate-do and --replicate-ignore options were not being
enforced on multi-table statements.
* Running out of diskspace in the location specified by the tmpdir
option resulted in incorrect error message.
* Test suite func_math test returned warnings when server not compiled
with InnoDB support. (Bug#15429 (http://bugs.mysql.com/15429))
* The MBROverlaps GIS function returned incorrect results.
* A CREATE TABLE ... SELECT ... on an equation involving DOUBLE values
could result in the table being created with columns too small to
hold the equation result. (Bug#9855 (http://bugs.mysql.com/9855))
* UPDATE statement crashed multi-byte character set FULLTEXT index if
update value was almost identical to initial value only differing in
some spaces being changed to " ";.
* Single table UPDATE statements without ORDER BY clauses which
updated the same indexed column that was being filtered on were
optimized with a full index scan instead of a more appropriate index
range scan. (Bug#15935 (http://bugs.mysql.com/15935))
* A prepared statement created from a SELECT ... LIKE query (such as
PREPARE stmt1 FROM 'SELECT col_1 FROM tedd_test WHERE col_1 LIKE ?';)
would begin to produce erratic results after being executed
repeatedly numerous (thousands) of times.
Changes in 4.1.17 (Not released)
Functionality added or changed:
* In the latin5_turkish_ci collation, the order of the characters A
WITH CIRCUMFLEX, I WITH CIRCUMLEX, and U WITH CIRCUMFLEX was
changed. If you have used these characters in any indexed columns,
you should rebuild those indexes.
* Support files for compiling with Visual Studio 6 have been removed.
* Internal sha1_result function renamed to mysql_sha1_result to
prevent conflicts with other projects.
* Performing a RENAME TABLE on an InnoDB table when the server is
started with the --innodb-file-per-table and the data directory is a
symlink caused a server crash.
* The mysql_stmt_attr_get function returned an unsigned int instead of
a boolean for STMT_ATTR_UPDATE_MAX_LENGTH.
* Characters in the gb2312 and euckr character sets which did not have
Unicode mappings were truncated.
* Piping the fill_help_tables.sql file into mysqld resulted in a
syntax error. (Bug#15965 (http://bugs.mysql.com/15965))
* NDBCluster: Upon the completion of a scan where a key request
remained outstanding on the primary replica and a starting node
died, the scan did not terminate. This caused incompleted error
handling of the failed node.
* Using CAST() to convert values with long fractional and/or exponent
parts to TIME returned wrong results.
* An INSERT ... SELECT statement between tables in a MERGE set can
return errors when statement involves insert into child table from
merge table or vice-versa. (Bug#5390 (http://bugs.mysql.com/5390))
* Certain permission management statements could create a NULL
hostname for a user, resulting in a server crash.
* For InnoDB tables, using a column prefix for a utf8 column in a
primary key caused Cannot find record errors when attempting to
locate records. (Bug#14056 (http://bugs.mysql.com/14056))
* Certain CREATE TABLE ... AS ... statements involving ENUM columns
could cause server crash. (Bug#12913 (http://bugs.mysql.com/12913))
* Using an aggregate function as the argument for a HAVING clause
would result in the aggregate function always returning FALSE.
* The COALESCE() function truncated data in a TINYTEXT column.
* InnoDB: Comparison of indexed VARCHAR CHARACTER SET ucs2 COLLATE
ucs2_bin columns using LIKE could fail.
* Issuing a DROP USER command could cause some users to encounter a
hostname is not allowed to connect to this MySQL server error.
* Access Denied error could be erroneously returned with specific
grant combinations under high load.
* Symbolic links did not function properly on Windows platforms.
* BDB: A DELETE, INSERT, or UPDATE of a BDB table could cause the
server to crash where the query contained a subquery using an index
read. (Bug#15536 (http://bugs.mysql.com/15536))
* DELETE could report full-text index corruption (Invalid key for
table ...) if the index was built with repair-by-sort, the data in
the full-text index used UCA collation, and some word appeared in
the data terminated by a 0xC2A0 character as well as by other
non-letter characters. (Bug#11336 (http://bugs.mysql.com/11336))
* A race condition when creating temporary files caused a deadlock on
Windows with threads in Opening tables or Waiting for table states.
* InnoDB: If FOREIGN_KEY_CHECKS was 0, InnoDB allowed inconsistent
foreign keys to be created.
* NDB Cluster: A memory leak occurred when performing ordered index
scans using indexes a columns larger than 32 bytes, which would
eventually lead to the forced shutdown of all mysqld server
processes used with the cluster.
* NDB Cluster: Under some circumstances, it was possible for a
restarting node to undergo a forced shutdown.
* NDB Cluster: If an abort by the Transaction Coordinator timed out,
the abort condition was incorrectly handled, causing the
transacviton record to be released prematurely.
* NDB Cluster: A node which failed during cluster startup was
sometimes not removed from the internal list of active nodes.
* NDB Cluster: There was a small window for a node failure to occur
during a backup without an error being reported.
* Multiple-table update operations were counting updates and not
updated rows. As a result, if a row had several updates it was
counted several times for the "rows matched" value but updated only
once. (Bug#15028 (http://bugs.mysql.com/15028))
* SELECT queries that began with an opening parenthesis were not being
placed in the query cache. (Bug#14652 (http://bugs.mysql.com/14652))
Kent Boortz, Senior Software Developer
MySQL AB, www.mysql.com
Office: +46 18 174400 ext. 4450 (VoIP)
Office: +46 19 182931
Mobile: +46 70 2791171
to post comments)