Forum Index
MYSQL discussions groups
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

MySQL-4.1.22 has been released

Post new topic   Reply to topic Forum Index -> MySQL Packagers
View previous topic :: View next topic  
Author Message
Mads Martin Joergensen

PostPosted: Mon Nov 27, 2006 8:17 pm    Post subject: MySQL-4.1.22 has been released Reply with quote

Dear MySQL Users,

MySQL 4.1.22, a new version of the popular Open Source Database
Management System, has been released. The MySQL server is now
available in source and binary form for a number of platforms from our
download pages at and mirror sites.

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

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 the final planned binary bugfix release for the MySQL 4.1
production family. Per the MySQL Product Life Cycle policy, active
support of version 4.1 will end on December 31, 2006. However, as stated
in the MySQL Product Life Cycle policy on

you can benefit from our extended lifecycle support during three
additional years via MySQL Enterprise. You can find more information
about MySQL Enterprise and watch demos of the Monitoring and Advisory
Service at:

For information on the most current version of the MySQL server, please

The following section documents all changes and bug fixes that have been
applied since the last official MySQL release. If you would like to
receive more fine-grained and personalized update alerts about fixes
that are relevant to the version and features you use, please consider
subscribing to MySQL Network (a commercial MySQL offering). For more
details please see

Functionality added or changed:
* The mysqld manpage has been reclassified from volume 1 to
volume 8. (Bug#21220:
* MySQL now can do stack dumps on x86_64 and i386/NPTL systems.
statements are deprecated. See Section, "LOAD DATA
FROM MASTER Syntax," for recommended alternatives.
* A warning now is issued if the client attempts to set the
SQL_LOG_OFF variable without the SUPER privilege.

Bugs fixed:
* Deleting entries from a large MyISAM index could cause index
corruption when it needed to shrink. Deletes from an index can
happen when a record is deleted, when a key changes and must
be moved, and when a key must be un-inserted because of a
duplicate key. This can also happen in REPAIR TABLE when a
duplicate key is found and in myisamchk when sorting the
records by an index. (Bug#22384:
* Setting myisam_repair_threads caused any repair operation on a
MyISAM table to fail to update the cardinality of indexes,
instead making them always equal to 1.
* Within a prepared statement, SELECT (COUNT(*) = 1) (or similar
use of other aggregate functions) did not return the correct
result for statement re-execution.
* DELETE IGNORE could hang for foreign key parent deletes.
* Redundant binary log LAST_INSERT_ID events could be generated;
LAST_INSERT_ID(expr) didn't return the value of expr;
LAST_INSERT_ID() could return the value generated by the
current statement if the call happens after value generation,
as in:
* FROM_UNIXTIME() did not accept arguments up to POWER(2,31)-1,
which it had previously.
* A literal string in a GROUP BY clause could be interpreted as
a column name. (Bug#14019:
* WITH ROLLUP could group unequal values.
* LIKE searches failed for indexed utf8 character columns.
* The optimizer sometimes mishandled R-tree indexes for GEOMETRY
data types, resulting in a server crash.
* Entries in the slow query log could have an incorrect
Rows_examined value. (Bug#12240:
* Insufficient memory (myisam_sort_buffer_size) could cause a
server crash for several operations on MyISAM tables: repair
table, create index by sort, repair by sort, parallel repair,
bulk insert. (Bug#23175:
* REPAIR TABLE ... USE_FRM could cause a server crash or hang
when used for a MyISAM table in a database other than the
default database. (Bug#22562:
* OPTIMIZE TABLE with myisam_repair_threads > 1 could result in
MyISAM table corruption.
* The result for CAST() when casting a value to UNSIGNED was
limited to the maximum signed BIGINT value
(9223372036854775808), not the maximum unsigned value
(18446744073709551615). (Bug#8663:
* For multiple-table UPDATE statements, storage engines were not
notified of duplicate-key errors.
* Successive invocations of a COUNT(*) query containing a join
on two MyISAM tables and a WHERE clause of the form WHERE
(table1.column1 = table2.column2) OR table2.column2 IS NULL
yielded different results.
* Using ALTER TABLE to add an ENUM column with an enumeration
value containing 0xFF caused the name of the first table
column to be lost. (Bug#20922:
* PROCEDURE ANALYSE() returned incorrect values of M FLOAT(M, D)
and DOUBLE(M, D). (Bug#20305:
* A query that used GROUP BY and an ALL or ANY quantified
subquery in a HAVING clause could trigger an assertion
failure. (Bug#21853:
* For an ENUM column that used the ucs2 character set, using
ALTER TABLE to modify the column definition caused the default
value to be lost. (Bug#20108:
* Creating a TEMPORARY table with the same name as an existing
table that was locked by another client could result in a lock
conflict for DROP TEMPORARY TABLE because the server
unnecessarily tried to acquire a name lock.
* Incorporated some portability fixes into the definition of
__attribute__ in my_global.h.
* In the package of pre-built time zone tables that is available
for download at,
the tables now explicitly use the utf8 character set so that
they work the same way regardless of the system character set
value. (Bug#21208:
* The build process incorrectly tried to overwrite
sql/lex_hash.h. This caused the build to fail when using a
shadow link tree pointing to original sources that were owned
by another account. (Bug#18888:
* Execution of a prepared statement that uses an IN subquery
with aggregate functions in the HAVING clause could cause a
server crash. (Bug#22085:
* Selecting from a MERGE table could result in a server crash if
the underlying tables had fewer indexes than the MERGE table
itself. (Bug#21617:,
* SUBSTR() results sometimes were stored improperly into a
temporary table when multi-byte character sets were used.
* Parallel builds occasionally failed on Solaris.
* The source distribution failed to compile when configured with
the --without-geometry option.
* The server returns a more informative error message when it
attempts to open a MERGE table that has been defined to use
non-MyISAM tables. (Bug#10974:
* On Mac OS X, zero-byte read() or write() calls to an
SMB-mounted filesystem could return a non-standard return
value, leading to data corruption. Now such calls are avoided.
VALUES(col_name) within the UPDATE clause sometimes was
handled incorrectly. (Bug#21555:
* Table aliases in multiple-table DELETE statements sometimes
were not resolved. (Bug#21392:
* EXPORT_SET() did not accept arguments with coercible character
sets. (Bug#21531:
* The --collation-server server option was being ignored. With
the fix for this problem, if you choose a non-default
character set with --character-set-server, you should also use
--collation-server to specify the collation.
* A subquery that uses an index for both the WHERE and ORDER BY
clauses produced an empty result.
* Queries containing a subquery that used aggregate functions
could return incorrect results.
* The MD5(), SHA1(), and ENCRYPT() functions should return a
binary string, but the result sometimes was converted to the
character set of the argument. MAKE_SET() and EXPORT_SET() now
use the correct character set for their default separators,
resulting in consistent result strings which can be coerced
according to normal character set rules.
* Use of myisampack or myisamchk on a compressed MyISAM table
with FULLTEXT indexing resulted in table corruption.
* The optimizer could produce an incorrect result after AND with
collations such as latin1_german2_ci, utf8_czech_ci, and
utf8_lithianian_ci. (Bug#9509:
* character_set_results can be NULL to signify "no conversion,"
but some code did not check for NULL, resulting in a server
crash. (Bug#21913:
* The myisam_stats_method variable was mishandled when set from
an option file or on the command line.
* libmysqld produced some warnings to stderr which could not be
silenced. These warnings now are suppressed.
* If a column definition contained a character set declaration,
but a DEFAULT value began with an introducer, the introducer
character set was used as the column character set.
* Some Linux-x86_64-icc packages (of previous releases)
mistakenly contained 32-bit binaries. Only ICC builds are
affected, not gcc builds. Solaris and FreeBSD x86_64 builds
are not affected. (Bug#22238:
* For TIME_FORMAT(), the %H and %k format specifiers can return
values larger than two digits (if the hour is greater than
99), but for some query results that contained three-character
hours, column values were truncated.
* For table-format output, mysql did not always calculate
columns widths correctly for columns containing multi-byte
characters in the column name or contents.
* Views could not be updated within a stored function or
trigger. (Bug#17591:
* Usernames have a maximum length of 16 characters (even if they
contain multi-byte characters), but were being truncated to 16
bytes. (Bug#20393:
* Database and table names have a maximum length of 64
characters (even if they contain multi-byte characters), but
were being truncated to 64 bytes.
* When using tables created under MySQL 4.1 with a 5.0 server,
if the tables contained VARCHAR columns, for some queries the
metadata sent to the client could have an empty column name.
* On 64-bit systems, use of the cp1250 character set with a
primary key column in a LIKE clause caused a server crash for
patterns having letters in the range 128..255.
* A subquery in the WHERE clause of the outer query and using IN
and GROUP BY returned an incorrect result.
* COUNT(*) queries with ORDER BY and LIMIT could return the
wrong result. (Bug#21787:
Note: This problem was introduced by the fix for
Bug#9676:, which limited the rows
stored in a temporary table to the LIMIT clause. This
optimization is not applicable to non-group queries with
aggregate functions. The current fix disables the optimization
in such cases.
* Running SHOW MASTER LOGS at the same time as binary log files
were being switched would cause mysqld to hang.
* Adding ORDER BY to a SELECT DISTINCT(expr) query could produce
incorrect results. (Bug#21456:
* For InnoDB tables, the server could crash when executing NOT
IN () subqueries. (Bug#21077:
* mysqld --flush failed to flush MyISAM table changes to disk
following an UPDATE statement for which no updated column had
an index. (Bug#20060:
* The --with-collation option was not honored for client
connections. (Bug#7192:
* NDB Cluster: Attempting to create an NDB table on a MySQL with
an existing non-Cluster table with the same name in the same
database could result in data loss or corruption. MySQL now
issues a warning when a SHOW TABLES or other statement causing
table discovery finds such a table.
* NDB Cluster (NDB API): Attempting to read a nonexistent tuple
using Commit mode for NdbTransaction::execute() caused node
failures. (Bug#22672:
* NDB Cluster: Restoring a cluster failed if there were any
tables with 128 or more columns.
table could lead to deadlocks and memory leaks.
* NDB Cluster: If a node restart could not be performed from the
REDO log, no node takeover took place. This could cause
partitions to be left empty during a system restart.
* NDB Cluster: Multiple node restarts in rapid succession could
cause a system restart to fail
(Bug#22892:, or induce a race
condition (Bug#23210:
* NDB Cluster: The node recovery algorithm was missing a version
check for tables in the ALTER_TABLE_COMMITTED state (as
opposed to the TABLE_ADD_COMMITTED state, which has the
version check). This could cause inconsistent schemas across
nodes following node recovery.
* NDB Cluster: The output for the --help option used with NDB
executable programs (ndbd, ndb_mgm, ndb_restore, ndb_config,
and so on) referred to the Ndb.cfg file, instead of my.cnf.
* NDB Cluster: The ndb_mgm management client did not set the
exit status on errors, always returning 0 instead.
* NDB Cluster: Cluster logs were not rotated following the first
rotation cycle. (Bug#21345:
* NDB Cluster: When inserting a row into an NDB table with a
duplicate value for a non-primary unique key, the error issued
would reference the wrong key.
* NDB Cluster: Under some circumstances, local checkpointing
would hang, keeping any unstarted nodes from being started.
* NDB Cluster: In some cases where SELECT COUNT(*) from an NDB
table should have yielded an error, MAX_INT was returned
instead. (Bug#19914:
* NDB Cluster: ndb_restore did not always make clear that it had
recovered successfully from temporary errors while restoring a
cluster backup. (Bug#19651:
* NDB Cluster: A problem with takeover during a system restart
caused ordered indexes to be rebuilt incorrectly.
* NDB Cluster: The ndb_mgm program was included in both the
MySQL-ndb-tools and MySQL-ndb-management RPM packages,
resulting in a conflict if both were installed. Now ndb_mgm is
included only in MySQL-ndb-tools.
* NDB Cluster: and ndb_error_reporter were missing
from RPM packages. (Bug#20426:
* NDB Cluster: Setting TransactionDeadlockDetectionTimeout to a
value greater than 12000 would cause scans to deadlock, time
out, fail to release scan records, until the cluster ran out
of scan records and stopped processing.
* NDB Cluster: The server provided a non-descriptive error
message when encountering a fatally corrupted REDO log.
* NDB Cluster: A partial rollback could lead to node restart
failures. (Bug#21536:
* NDB Cluster: The failure of a unique index read due to an
invalid schema version could be handled incorrectly in some
cases, leading to unpredictable results.
* NDB Cluster: In a cluster with more than 2 replicas, a manual
restart of one of the data nodes could fail and cause the
other nodes in its nodegroup to shut down.
* NDB Cluster: When the redo buffer ran out of space, a Pointer
too large error was raised and the cluster could become
unusable until restarted with --initial.
* NDB Cluster: In some situations with a high disk-load, writing
of the redo log could hang, causing a crash with the error
message GCP STOP detected.
* NDB Cluster: and ndb_error_reporter were missing
from RPM packages. (Bug#20426:
* NDB Cluster: The server failed with a non-descriptive error
message when out of data memory.
* NDB Cluster: SELECT ... FOR UPDATE failed to lock the selected
rows. (Bug#18184:
* NDB Cluster: Some queries involving joins on very large NDB
tables could crash the MySQL server.
* Character set collation was ignored in GROUP BY clauses.
* A query using WHERE column = constant OR column IS NULL did
not return consistent results on successive invocations. The
column in each part of the WHERE clause could be either the
same column, or two different columns, for the effect to be
observed. (Bug#21019:
* A query using WHERE NOT (column < ANY (subquery)) yielded a
different result from the same query using the same column and
subquery with WHERE (column > ANY (subquery)).
* Using the extended syntax for TRIM() --- that is, TRIM(...
FROM ...) --- caused erroneous output from EXPLAIN EXTENDED
statements. (Bug#17526:
* DELETE with WHERE condition on a BTREE-indexed column for a
MEMORY table deleted only the first matched row.
* For cross-database multiple-table UPDATE statements, a user
with all privileges for the default database could update
tables in another database for which the user did not have
UPDATE privileges. (Bug#7391:
* mysql_install_db incorrectly had a blank first line.
* Under heavy load (executing more than 1024 simultaneous
complex queries), a problem in the code that handles internal
temporary tables could lead to writing beyond allocated space
and memory corruption.
* Multiple invocations of the REVERSE() function could return
different results. (Bug#18243:
* Conversion of TIMESTAMP values between UTC and the local time
zone resulted in some values having the year 2069 rather than
1969. (Bug#16327:
* Under certain circumstances, AVG(key_val) returned a value but
MAX(key_val) returned an empty set due to incorrect
application of MIN()/MAX() optimization.
* Using aggregate functions in subqueries yielded incorrect
results under certain circumstances due to incorrect
application of MIN()/MAX() optimization.
* Using > ALL with subqueries that return no rows yielded
incorrect results under certain circumstances due to incorrect
application of MIN()/MAX() optimization.
* Using ANY with "non-table" subqueries such as SELECT 1 yielded
incorrect results under certain circumstances due to incorrect
application of MIN()/MAX() optimization.
* The use of WHERE col_name IS NULL in SELECT statements reset
the value of LAST_INSERT_ID() to zero.
* Use of the join cache in favor of an index for ORDER BY
operations could cause incorrect result sorting.
* libmysqld returned TEXT columns to the client as number of
bytes, not number of characters (which can be different for
multi-byte character sets).

Mads Martin

Mads Martin Jørgensen, Release Manager
MySQL AB, Odense, Denmark --
Back to top
Display posts from previous:   
Post new topic   Reply to topic Forum Index -> MySQL Packagers All times are GMT
Page 1 of 1

Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB © 2001, 2006 phpBB Group
Perl Forums  |  Education Forums  |  Learning Forums  |  File Systems Forums  |  Lustre / XFS Forums
SEO toolkit © 2004-2006 webmedic