=======================================================================

Changes in MySQL 5.1.58 (July 5th, 2011)

Bugs fixed:

* InnoDB Storage Engine: If the server crashed while an XA

transaction was prepared but not yet committed, the

transaction could remain in the system after restart, and

cause a subsequent shutdown to hang. (Bug #11766513, Bug

#59641)

* Partitioning: When executing a row-ordered retrieval index

merge, the partitioning handler used memory from that

allocated for the table, rather than allocated to the

query, causing table object memory not to be freed until the

table was closed. (Bug #11766249, Bug #59316)

* Replication: When mysqlbinlog was invoked using

–base64-output=decode-row and –start-position=pos, (where

pos is a point in the binary log past the format description

log event), a spurious error of the type shown here was

generated:

malformed binlog: it does not contain any Format_description_log_event…

However, since there is nothing unsafe about not printing the

format description log event, the error has been removed for

this case. (Bug #12354268)

* Replication: Typographical errors appeared in the text of

several replication error messages. (The word “position” was

misspelled as “postion”.) (Bug #11762616, Bug #55229)

* After the fix for Bug#11889186, MAKEDATE() arguments with a

year part greater than 9999 raised an assertion. (Bug

#12403504)

* An assertion could be raised due to a missing NULL value check

in Item_func_round::fix_length_and_dec(). (Bug #12392636)

* In debug builds on Solaris, an assertion was raised if a

reverse IP lookup with gethostbyaddr_r() failed. (Bug

#12377872)

* MySQL did not build if configured with both –with-debug and

–with-libedit. (Bug #12329909)

* A problem introduced in 5.1.57 caused very old (MySQL 4.0)

clients to be unable to connect to the server. (Bug #61222,

Bug #12563279)

* Using CREATE EVENT IF NOT EXISTS for an event that already

existed and was enabled caused multiple instances of the event

to run. (Bug #61005, Bug #12546938)

* The incorrect max_length value for YEAR values could be used

in temporary result tables for UNION, leading to incorrect

results. (Bug #59343, Bug #11766270)

* In Item_func_in::fix_length_and_dec(), a Valgrind warning for

uninitialized values was corrected. (Bug #59270, Bug

#11766212)

* In ROUND() calculations, a Valgrind warning for uninitialized

memory was corrected. (Bug #58937, Bug #11765923)

* Valgrind warnings caused by comparing index values to an

uninitialized field were corrected. (Bug #58705, Bug

#11765713)

* LOAD DATA INFILE errors could leak I/O cache memory. (Bug

#58072, Bug #11765141)

* For LOAD DATA INFILE, multibyte character sequences could be

pushed onto a stack too small to accommodate them. (Bug

#58069, Bug #11765139)

* An embedded client would abort rather than issue an error

message if it issued a TEE command (\T file_name) and the

directory containing the file did not exist. This occurred

because the wrong error handler was called. (Bug #57491, Bug

#11764633)

* In debug builds, Field_new_decimal::store_value() was subject

to buffer overflows. (Bug #55436, Bug #11762799)

* On Linux, the mysql client built using the bundled libedit did

not read ~/.editrc. (Bug #49967, Bug #11757855)

* The optimizer sometimes incorrectly processed HAVING clauses

for queries that did not also have an ORDER BY clause. (Bug

#48916, Bug #11756928)

* PROCEDURE ANALYZE() could leak memory for NULL results, and

could return incorrect results if used with a LIMIT clause.

(Bug #48137, Bug #11756242)

* On some platforms, the Incorrect value: xxx for column yyy at

row zzz error produced by LOAD DATA INFILE could have an

incorrect value of zzz. (Bug #46895, Bug #11755168)

* In MySQL 5.1 and up, if a table had triggers that used syntax

supported in 5.0 but not 5.1, the table became unavailable.

Now the table is marked as having broken triggers. (Bug

#45235, Bug #11753738)

* An attempt to install nonexistent files during installation

was corrected. (Bug #43247, Bug #11752142)

* On FreeBSD 64-built builds of the embedded server, exceptions

were not prevented from propagating into the embedded

application. (Bug #38965, Bug #11749418)

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1.

Changes in MySQL 5.1.56 (01 March 2011):

Functionality added or changed:

* mysqldump –xml now displays comments from column definitions.

(Bug #13618)

Bugs fixed:

* InnoDB Storage Engine: InnoDB returned values for

“rows examined” in the query plan that were higher than

expected. NULL values were treated in an inconsistent way. The

inaccurate statistics could trigger “false positives” in

combination with the MAX_JOIN_SIZE setting, because the

queries did not really examine as many rows as reported.

(Bug #30423)

* Partitioning: Trying to use the same column more than once in

the partitioning key when partitioning a table by KEY caused

mysqld to crash. Such duplication of key columns is now

expressly disallowed, and fails with an appropriate error.

(Bug #53354, Bug #57924)

* Replication: When using the statement-based logging format,

INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements

affecting transactional tables that did not fail were not

written to the binary log if they did not insert any rows.

(With statement-based logging, all successful statements

should be logged, whether they do or do not cause any rows to

be changed.) (Bug #59338)

* Replication: Formerly, STOP SLAVE stopped the slave I/O thread

first and then stopped the slave SQL thread; thus, it was

possible for the I/O thread to stop after replicating only

part of a transaction which the SQL thread was executing, in

wich case—if the transaction could not be rolled back

safely—the SQL thread could hang.

Now, STOP SLAVE stops the slave SQL thread first and then

stops the I/O thread; this guarantees that the I/O thread can

fetch any remaining events in the transaction that the SQL

thread is executing, so that the SQL thread can finish the

transaction if it cannot be rolled back safely. (Bug #58546)

* A query of the following form returned an incorrect result,

where the values for col_name in the result set were entirely

replaced with NULL values:

SELECT DISTINCT col_name … ORDER BY col_name DESC;

(Bug #59308, Bug #11766241)

* DELETE or UPDATE statements could fail if they used DATE or

DATETIME values with a year, month, or day part of zero.

(Bug #59173)

* The ESCAPE clause for the LIKE operator allows only

expressions that evaluate to a constant at execution time, but

aggregrate functions were not being rejected. (Bug #59149)

* Memory leaks detected by Valgrind, some of which could cause

incorrect query results, were corrected. (Bug #59110, Bug

#11766075)

* mysqlslap failed to check for a NULL return from

mysql_store_result() and crashed trying to process the result

set. (Bug #59109)

* In debug builds, SUBSTRING_INDEX(FORMAT(…), FORMAT(…))

could cause a server crash. (Bug #58371)

* When mysqldadmin was run with the –sleep and –count options,

it went into an infinite loop executing the specified command.

(Bug #58221)

* Some string manipulating SQL functions use a shared string

object intended to contain an immutable empty string. This

object was used by the SQL function SUBSTRING_INDEX() to

return an empty string when one argument was of the wrong

datatype. If the string object was then modified by the SQL

function INSERT(), undefined behavior ensued. (Bug #58165, Bug

#11765225)

* Parsing nested regular expressions could lead to recursion

resulting in a stack overflow crash. (Bug #58026, Bug

#11765099)

* The mysql client went into an infinite loop if the standard

input was a directory. (Bug #57450)

* The expression const1 BETWEEN const2 AND field was optimized

incorrectly and produced incorrect results.

(Bug #57030, Bug #11764215)

* Some RPM installation scripts used a hardcoded value for the

data directory, which could result in a failed installation

for users who have a nonstandard data directory location. The

same was true for other configuration values such as the PID

file name. (Bug #56581, Bug #11763817)

* On FreeBSD and OpenBSD, the server incorrectly checked the

range of the system date, causing legal values to be rejected.

(Bug #55755, Bug #11763089)

* When using ExtractValue() or UpdateXML(), if the XML to be

read contained an incomplete XML comment, MySQL read beyond

the end of the XML string when processing, leading to a crash

of the server. (Bug #44332)

For an overview of what’s new in MySQL 5.1, please see  http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.52 on new servers or upgrading to MySQL 5.1.52 from previous MySQL releases, please see  http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of platforms from our download pages at  http://dev.mysql.com/downloads/

For information on open issues in MySQL 5.1, please see the errata list at  http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1.  It may also be viewed online at  http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html

=======================================================================

C.1.1. Changes in MySQL 5.1.52 (11 October 2010)

Bugs fixed:

* InnoDB Storage Engine: InnoDB incorrectly reported an error

when a cascading foreign key constraint deleted more than 250

rows. (Bug#57255: http://bugs.mysql.com/bug.php?id=57255)

* InnoDB Storage Engine: A SELECT … FOR UPDATE statement

affecting a range of rows in an InnoDB table could cause a

crash in the debug version of the server.

(Bug#56716: http://bugs.mysql.com/bug.php?id=56716)

* InnoDB Storage Engine: Improved the performance of UPDATE

operations on InnoDB tables, when only non-indexed columns are

changed. (Bug#56340: http://bugs.mysql.com/bug.php?id=56340)

* InnoDB Storage Engine: The server could crash on shutdown, if

started with –innodb-use-system-malloc=0.

(Bug#55627: http://bugs.mysql.com/bug.php?id=55627)

* InnoDB Storage Engine: Setting the PACK_KEYS=0 table option

for an InnoDB table prevented new indexes from being added to

the table. (Bug#54606: http://bugs.mysql.com/bug.php?id=54606)

* InnoDB Storage Engine: Changed the locking mechanism for the

InnoDB data dictionary during ROLLBACK operations, to improve

concurrency for REPLACE statements.

(Bug#54538: http://bugs.mysql.com/bug.php?id=54538)

* InnoDB Storage Engine: InnoDB transactions could be

incorrectly committed during recovery, rather than rolled

back, if the server crashed and was restarted after performing

ALTER TABLE…ADD PRIMARY KEY on an InnoDB table, or some

other operation that involves copying the entire table.

(Bug#53756: http://bugs.mysql.com/bug.php?id=53756)

* Partitioning: Replication: Attempting to execute LOAD DATA on

a partitioned MyISAM table while using statement-based logging

mode caused the master to hang or crash.

(Bug#51851: http://bugs.mysql.com/bug.php?id=51851)

* Partitioning: Multi-table UPDATE statements involving a

partitioned MyISAM table could cause this table to become

corrupted. Not all tables affected by the UPDATE needed to be

partitioned for this issue to be observed.

(Bug#55458: http://bugs.mysql.com/bug.php?id=55458)

* Partitioning: EXPLAIN PARTITIONS returned bad estimates for

range queries on partitioned MyISAM tables. In addition,

values in the rows column of EXPLAIN PARTITIONS output did not

take partition pruning into account.

(Bug#53806: http://bugs.mysql.com/bug.php?id=53806,

Bug#46754: http://bugs.mysql.com/bug.php?id=46754)

* Replication: Backticks used to enclose identifiers for

savepoints were not preserved in the binary log, which could

lead to replication failure when the identifier, stripped of

backticks, could be misinterpreted, causing a syntax or other

error.

This could cause problems with MySQL application programs

making use of generated savepoint IDs. If, for instance,

java.sql.Connection.setSavepoint() is called without any

parameters, Connector/J automatically generates a savepoint

identifier consisting of a string of hexadecimal digits 0-F

encased in backtick (`) characters. If such an ID took the

form `NeN` (where N represents a string of the decimal digits

0-9, and e is a literal uppercase or lowercase “E” character).

Removing the backticks when writing the identifier into the

binary log left behind a substring which the slave MySQL

server tried to interpret as a floating point number, rather

than as an identifier. The resulting syntax error caused loss

of replication.

(Bug#55961: http://bugs.mysql.com/bug.php?id=55961)

See also Bug#55962: http://bugs.mysql.com/bug.php?id=55962.

* If a query specified a DATE or DATETIME value in a format

different from ‘YYYY-MM-DD HH:MM:SS’, a greater-than-or-equal

(>=) condition matched only greater-than values in an indexed

TIMESTAMP column.

(Bug#55779: http://bugs.mysql.com/bug.php?id=55779)

* If there was an active SELECT statement, an error arising

during trigger execution could cause a server crash.

(Bug#55421: http://bugs.mysql.com/bug.php?id=55421)

* With an UPDATE IGNORE statement including a subquery that was

evaluated using a temporary table, an error transferring the

data from the temporary was ignored, causing an assertion to

be raised. (Bug#54543: http://bugs.mysql.com/bug.php?id=54543)

* Row subqueries producing no rows were not handled as UNKNOWN

values in row comparison expressions.

(Bug#54190: http://bugs.mysql.com/bug.php?id=54190)

* In some cases, when the left part of a NOT IN subquery

predicate was a row and contained NULL values, the query

result was incorrect.

(Bug#51070: http://bugs.mysql.com/bug.php?id=51070)

* For some queries, the optimizer produced incorrect results

using the Index Merge access method with InnoDB tables.

(Bug#50402: http://bugs.mysql.com/bug.php?id=50402)

* EXPLAIN produced an incorrect rows value for queries evaluated

using an index scan and that included LIMIT, GROUP BY, and

ORDER BY on a computed column.

(Bug#50394: http://bugs.mysql.com/bug.php?id=50394)

* mysql_store_result() and mysql_use_result() are not for use

with prepared statements and are not intended to be called

following mysql_stmt_execute(), but failed to return an error

when invoked that way.

(Bug#47485: http://bugs.mysql.com/bug.php?id=47485)

* A malformed packet sent by the server when the query cache was

in use resulted in lost-connection errors.

(Bug#42503: http://bugs.mysql.com/bug.php?id=42503)

* CREATE TABLE failed if a column referred to in an index

definition and foreign key definition was in different

lettercases in the two definitions.

(Bug#39932: http://bugs.mysql.com/bug.php?id=39932)

For an overview of what’s new in MySQL 5.1, please see  http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.51 on new servers or upgrading to MySQL 5.1.51 from previous MySQL releases, please see  http://dev.mysql.com/doc/refman/5.1/en/installing.html

=======================================================================

C.1.1. Changes in MySQL 5.1.51 (10 September 2010)

InnoDB Notes:

* InnoDB Plugin has been upgraded to version 1.0.12. This

version is considered of General Availability (GA) quality.

In this release, the InnoDB Plugin is included in source and

binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,

x86_64, ia64), generic Linux RPM packages, and any builds

produced with the icc compiler. It also does not work for

FreeBSD 6 and HP-UX or for Linux on generic ia64.

Bugs fixed:

* Incompatible Change: Replication: As of MySQL 5.5.6, handling

of CREATE TABLE IF NOT EXISTS … SELECT statements has been

changed for the case that the destination table already

exists:

+ Previously, for CREATE TABLE IF NOT EXISTS … SELECT,

MySQL produced a warning that the table exists, but

inserted the rows and wrote the statement to the binary

log anyway. By contrast, CREATE TABLE … SELECT (without

IF NOT EXISTS) failed with an error, but MySQL inserted

no rows and did not write the statement to the binary

log.

+ MySQL now handles both statements the same way when the

destination table exists, in that neither statement

inserts rows or is written to the binary log. The

difference between them is that MySQL produces a warning

when IF NOT EXISTS is present and an error when it is

not.

This change in handling of IF NOT EXISTS results in an

incompatibility for statement-based replication from a MySQL

5.1 master with the original behavior and a MySQL 5.5 slave

with the new behavior. Suppose that CREATE TABLE IF NOT EXISTS

… SELECT is executed on the master and the destination table

exists. The result is that rows are inserted on the master but

not on the slave. (Row-based replication does not have this

problem.)

To address this issue, statement-based binary logging for

CREATE TABLE IF NOT EXISTS … SELECT is changed in MySQL 5.1

as of 5.1.51:

+ If the destination table does not exist, there is no

change: The statement is logged as is.

+ If the destination table does exist, the statement is

logged as the equivalent pair of CREATE TABLE IF NOT

EXISTS and INSERT … SELECT statements. (If the SELECT

in the original statement is preceded by IGNORE or

REPLACE, the INSERT becomes INSERT IGNORE or REPLACE,

respectively.)

This change provides forward compatibility for statement-based

replication from MySQL 5.1 to 5.5 because when the destination

table exists, the rows will be inserted on both the master and

slave. To take advantage of this compatibility measure, the

5.1 server must be at least 5.1.51 and the 5.5 server must be

at least 5.5.6.

To upgrade an existing 5.1-to-5.5 replication scenario,

upgrade the master first to 5.1.51 or higher. Note that this

differs from the usual replication upgrade advice of upgrading

the slave first.

A workaround for applications that wish to achieve the

original effect (rows inserted regardless of whether the

destination table exists) is to use CREATE TABLE IF NOT EXISTS

and INSERT … SELECT statements rather than CREATE TABLE IF

NOT EXISTS … SELECT statements.

Along with the change just described, the following related

change was made: Previously, if an existing view was named as

the destination table for CREATE TABLE IF NOT EXISTS …

SELECT, rows were inserted into the underlying base table and

the statement was written to the binary log. As of MySQL

5.1.51 and 5.5.6, nothing is inserted or logged.

(Bug#47442: http://bugs.mysql.com/bug.php?id=47442,

Bug#47132: http://bugs.mysql.com/bug.php?id=47132,

Bug#48814: http://bugs.mysql.com/bug.php?id=48814,

Bug#49494: http://bugs.mysql.com/bug.php?id=49494)

* Incompatible Change: Previously, if you flushed the logs using

FLUSH LOGS or mysqladmin flush-logs and mysqld was writing the

error log to a file (for example, if it was started with the

–log-error option), it renamed the current log file with the

suffix -old, then created a new empty log file. This had the

problem that a second log-flushing operation thus caused the

original error log file to be lost unless you saved it under a

different name. For example, you could use the following

commands to save the file:

shell> mysqladmin flush-logs

shell> mv host_name.err-old backup-directory

To avoid the preceding file-loss problem, renaming no longer

occurs. The server merely closes and reopens the log file. To

rename the file, you can do so manually before flushing. Then

flushing the logs reopens a new file with the original file

name. For example, you can rename the file and create a new

one using the following commands:

shell> mv host_name.err host_name.err-old

shell> mysqladmin flush-logs

shell> mv host_name.err-old backup-directory

(Bug#29751: http://bugs.mysql.com/bug.php?id=29751)

* Partitioning: When the storage engine used to create a

partitioned table was disabled, attempting to drop the table

caused the server to crash.

(Bug#46086: http://bugs.mysql.com/bug.php?id=46086)

* If a view was named as the destination table for CREATE TABLE

… SELECT, the server produced a warning whether or not IF

NOT EXISTS was used. Now it produces a warning only when IF

NOT EXISTS is used, and an error otherwise.

(Bug#55777: http://bugs.mysql.com/bug.php?id=55777)

* The CHECK TABLE command could cause a time-consuming

verification of the InnoDB adaptive hash index memory

structure. Now this extra checking is only performed in

binaries built for debugging.

(Bug#55716: http://bugs.mysql.com/bug.php?id=55716)

* After the fix for

Bug#39653: http://bugs.mysql.com/bug.php?id=39653, the

shortest available secondary index was used for full table

scans. The primary clustered key was used only if no secondary

index could be used. However, when the chosen secondary index

includes all columns of the table being scanned, it is better

to use the primary index because the amount of data to scan is

the same but the primary index is clustered. This is now taken

into account.

(Bug#55656: http://bugs.mysql.com/bug.php?id=55656)

* (Bug#55627: http://bugs.mysql.com/bug.php?id=55627)

* The server was not checking for errors generated during the

execution of Item::val_xxx() methods when copying data to a

group, order, or distinct temp table’s row.

(Bug#55580: http://bugs.mysql.com/bug.php?id=55580)

* ORDER BY clauses that included user variable expressions could

cause a debug assertion to be raised.

(Bug#55565: http://bugs.mysql.com/bug.php?id=55565)

* Queries involving predicates of the form const NOT BETWEEN

not_indexed_column AND indexed_column could return incorrect

data due to incorrect handling by the range optimizer.

(Bug#54802: http://bugs.mysql.com/bug.php?id=54802)

* MIN() or MAX() with a subquery argument could raise a debug

assertion for debug builds or return incorrect data for

nondebug builds.

(Bug#54465: http://bugs.mysql.com/bug.php?id=54465)

* INFORMATION_SCHEMA plugins with no deinit() method resulted in

a memory leak.

(Bug#54253: http://bugs.mysql.com/bug.php?id=54253)

* After ALTER TABLE was used on a temporary transactional table

locked by LOCK TABLES, any later attempts to execute LOCK

TABLES or UNLOCK TABLES caused a server crash.

(Bug#54117: http://bugs.mysql.com/bug.php?id=54117)

* INSERT IGNORE INTO … SELECT statements could cause a debug

assertion to be raised.

(Bug#54106: http://bugs.mysql.com/bug.php?id=54106)

* The fix for Bug#30234: http://bugs.mysql.com/bug.php?id=30234

caused the server to reject the DELETE tbl_name.* … Access

compatibility syntax for multiple-table DELETE statements.

(Bug#53034: http://bugs.mysql.com/bug.php?id=53034)

* Enumeration plugin variables were subject to a type casting

error, causing inconsistent results between different

platforms. (Bug#42144: http://bugs.mysql.com/bug.php?id=42144)

* A PKG install on Solaris put some files in incorrect

locations. (Bug#31058: http://bugs.mysql.com/bug.php?id=31058)

For an overview of what’s new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.50 on new servers or upgrading to MySQL 5.1.50 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html

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

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

For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

C.1.1. Changes in MySQL 5.1.50 (03 August 2010)

    InnoDB Notes:

      * InnoDB Plugin has been upgraded to version 1.0.11. This
        version is considered of General Availability (GA) quality.
        In this release, the InnoDB Plugin is included in source and
        binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,
        x86_64, ia64), generic Linux RPM packages, and any builds
        produced with the icc compiler. It also does not work for
        FreeBSD 6 and HP-UX or for Linux on generic ia64.

    Bugs fixed:

      * Important Change: Replication: The LOAD DATA INFILE statement
        is now considered unsafe for statement-based replication. When
        using statement-based logging mode, the statement now produces
        a warning; when using mixed-format logging, the statement is
        made using the row-based format.
        (Bug#34283: http://bugs.mysql.com/bug.php?id=34283)

      * Partitioning: UPDATE and INSERT statements affecting
        partitioned tables performed poorly when using row-based
        replication.
        (Bug#52517: http://bugs.mysql.com/bug.php?id=52517)

      * Partitioning: INSERT ON DUPLICATE KEY UPDATE statements
        performed poorly on tables having many partitions. This was
        because the handler function for reading a row from a specific
        index was not optimized in the partitioning handler.
        (Bug#52455: http://bugs.mysql.com/bug.php?id=52455)

      * The server could crash on shutdown, if started with
        --innodb-use-system-malloc=0.
        (Bug#55581: http://bugs.mysql.com/bug.php?id=55581)

      * GROUP BY operations used max_sort_length inconsistently.
        (Bug#55188: http://bugs.mysql.com/bug.php?id=55188)

      * Building MySQL on Solaris 8 x86 failed when using Sun Studio
        due to gcc inline assembler code.
        (Bug#55061: http://bugs.mysql.com/bug.php?id=55061)

      * In debug builds, an assertion could be raised when the server
        tried to send an OK packet to the client after having failed
        to detect errors during processing of the WHERE condition of
        an UPDATE statement.
        (Bug#54734: http://bugs.mysql.com/bug.php?id=54734)

      * The database server could crash when renaming a table that had
        active transactions. (This issue only affected the database
        server when built for debugging.)
        (Bug#54453: http://bugs.mysql.com/bug.php?id=54453)

      * The server could crash during the recovery phase of startup,
        if it previously crashed while inserting BLOB or other large
        columns that use off-page storage into an InnoDB table created
        with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT.
        (Bug#54408: http://bugs.mysql.com/bug.php?id=54408)

      * For an InnoDB table created with ROW_FORMAT=COMPRESSED or
        ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED
        isolation level could cause the server to stop with an
        assertion error, if BLOB or other large columns that use
        off-page storage were being inserted at the same time.
        (Bug#54358: http://bugs.mysql.com/bug.php?id=54358)

      * A client could supply data in chunks to a prepared statement
        parameter other than of type TEXT or BLOB using the
        mysql_stmt_send_long_data() C API function (or
        COM_STMT_SEND_LONG_DATA command). This led to a crash because
        other data types are not valid for long data.
        (Bug#54041: http://bugs.mysql.com/bug.php?id=54041)

      * mysql_secure_installation did not properly identify local
        accounts and could incorrectly remove nonlocal root accounts.
        (Bug#54004: http://bugs.mysql.com/bug.php?id=54004)

      * Transactions could be incorrectly committed during recovery,
        rather than rolled back, if the server crashed and was
        restarted after performing ALTER TABLE...ADD PRIMARY KEY on an
        InnoDB table, or some other operation that involves copying
        the entire table.
        (Bug#53756: http://bugs.mysql.com/bug.php?id=53756)

      * Portability problems in SHOW STATUS could lead to incorrect
        results on some platforms.
        (Bug#53493: http://bugs.mysql.com/bug.php?id=53493)

      * Builds of MySQL generated a large number of warnings.
        (Bug#53445: http://bugs.mysql.com/bug.php?id=53445)

      * With lower_case_table_names set to a nonzero value, searches
        for table or database names in INFORMATION_SCHEMA tables could
        produce incorrect results.
        (Bug#53095: http://bugs.mysql.com/bug.php?id=53095)

      * The ABI check for MySQL failed to compile with gcc 4.5.
        (Bug#52514: http://bugs.mysql.com/bug.php?id=52514)

      * mysql_secure_installation sometimes failed to locate the mysql
        client. (Bug#52274: http://bugs.mysql.com/bug.php?id=52274)

      * Reading a ucs2 data file with LOAD DATA INFILE was subject to
        three problems. 1) Incorrect parsing of the file as ucs2 data,
        resulting in incorrect length of the parsed string. This is
        fixed by truncating the invalid trailing bytes (incomplete
        multibyte characters) when reading from the file. 2) Reads
        from a proper ucs2 file did not recognize newline characters.
        This is fixed by first checking whether a byte is a newline
        (or any other special character) before reading it as a part
        of a multibyte character. 3) When using user variables to hold
        column data, the character set of the user variable was set
        incorrectly to the database charset. This is fixed by setting
        it to the character set specified in the LOAD DATA INFILE
        statement, if any.
        (Bug#51876: http://bugs.mysql.com/bug.php?id=51876)

      * Searches in INFORMATION_SCHEMA tables for rows matching a
        nonexistent database produced an error instead of an empty
        query result.
        (Bug#49542: http://bugs.mysql.com/bug.php?id=49542)

      * On FreeBSD, memory mapping for MERGE tables could fail if
        underlying tables were empty.
        (Bug#47139: http://bugs.mysql.com/bug.php?id=47139)

      * The my_like_range_xxx() functions returned badly formed
        maximum strings for Asian character sets, which caused
        problems for storage engines.
        (Bug#45012: http://bugs.mysql.com/bug.php?id=45012)

      * A debugging assertion could be raised after a write failure to
        a closed socket.
        (Bug#42496: http://bugs.mysql.com/bug.php?id=42496)

      * An assertion failure occurred within yaSSL for very long keys.
        (Bug#29784: http://bugs.mysql.com/bug.php?id=29784)
        See also Bug#53463: http://bugs.mysql.com/bug.php?id=53463.

For an overview of what’s new in MySQL 5.1, please see  http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.46 on new servers or upgrading to MySQL 5.1.46 from previous MySQL releases, please see  http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of platforms from the download pages at  http://dev.mysql.com/downloads/

For information on open issues in MySQL 5.1, please see the errata list at  http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1.  It may also be viewed online at  http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html

=======================================================================

C.1.2. Changes in MySQL 5.1.46

InnoDB Plugin Notes:

* InnoDB Plugin has been upgraded to version 1.0.7. This version

is considered of General Availability (GA) quality. The InnoDB

Plugin Change History

(http://www.innodb.com/doc/innodb_plugin-1.0/innodb-changes.ht

ml) may contain information in addition to those changes

reported here.

In this release, the InnoDB Plugin is included in source and

binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,

x86_64, ia64), and generic Linux RPM packages. It also does

not work for FreeBSD 6 and HP-UX or for Linux on generic ia64.

Functionality added or changed:

* There is a new system variable, skip_name_resolve, that is set

from the value of the –skip-name-resolve server option. This

provides a way to determine at runtime whether the server uses

name resolution for client connections.

(Bug#37168: http://bugs.mysql.com/bug.php?id=37168)

Bugs fixed:

* Security Fix: Privilege checking for UNINSTALL PLUGIN was

incorrect. (Bug#51770: http://bugs.mysql.com/bug.php?id=51770)

* Partitioning: Partition pruning on RANGE partitioned tables

did not always work correctly; the last partition was not

excluded if the range was beyond it (when not using MAXVALUE).

Now the last partition is not included if the partitioning

function value is not within the range.

(Bug#51830: http://bugs.mysql.com/bug.php?id=51830)

* Partitioning: The insert_id server system variable was not

reset following an insert that failed on a partitioned MyISAM

table having an AUTO_INCREMENT column.

(Bug#50392: http://bugs.mysql.com/bug.php?id=50392)

* Partitioning: Foreign keys are not supported on partitioned

tables. However, it was possible via an ALTER TABLE statement

to set a foreign key on a partitioned table; it was also

possible to partition a table with a single foreign key.

(Bug#50104: http://bugs.mysql.com/bug.php?id=50104)

* Partitioning: GROUP BY queries performed poorly for some

partitioned tables. This was due to the block size not being

set for partitioned tables, thus the keys per block was not

correct, which could cause such queries to be optimized

incorrectly.

(Bug#48229: http://bugs.mysql.com/bug.php?id=48229)

See also Bug#37252: http://bugs.mysql.com/bug.php?id=37252.

* Partitioning: REPAIR TABLE failed for partitioned ARCHIVE

tables. (Bug#46565: http://bugs.mysql.com/bug.php?id=46565)

* Replication: TRUNCATE TABLE performed on a temporary table

using the InnoDB storage engine was logged even when using

row-based mode.

(Bug#51251: http://bugs.mysql.com/bug.php?id=51251)

* Replication: When using temporary tables the binary log needs

to insert a pseudo-thread ID for threads that are using

temporary tables, each time a switch happens between two

threads, both of which are using temporary tables. However, if

a thread issued a failing statement before exit, its ID was

not recorded in the binary log, and this in turn caused the ID

for the next thread that tried to do something with a

temporary table not to be logged as well. Subsequent replays

of the binary log failed with the error Table … doesn’t

exist. (Bug#51226: http://bugs.mysql.com/bug.php?id=51226)

* Replication: If the master was using sql_mode=’TRADITIONAL’,

duplicate key errors were not sent to the slave, which

received 0 rather than the expected error code. This caused

replication to fail even when such an error was expected.

(Bug#51055: http://bugs.mysql.com/bug.php?id=51055)

* Replication: When run with the –database option, mysqlbinlog

printed ROLLBACK statements but did not print any

corresponding SAVEPOINT statements.

(Bug#50407: http://bugs.mysql.com/bug.php?id=50407)

* Replication: CREATE EVENT statements were padded with

“garbage” characters when written to the binary log, which

caused a syntax error when trying to read back from the log.

(Bug#50095: http://bugs.mysql.com/bug.php?id=50095)

* Replication: Column length information generated by InnoDB did

not match that generated by MyISAM, which caused invalid

metadata to be written to the binary log when trying to

replicate BIT columns.

(Bug#49618: http://bugs.mysql.com/bug.php?id=49618)

* Replication: The value of Slave_IO_running in the output of

SHOW SLAVE STATUS did not distinguish between all 3 possible

states of the slave I/O thread (not running; running but not

connected; connected). Now the value Connecting (rather than

No) is shown when the slave I/O thread is running but the

slave is not connected to a replication master.

The server system variable Slave_running also reflects this

change, and is now consistent with what is shown for

Slave_IO_running.

(Bug#30703: http://bugs.mysql.com/bug.php?id=30703,

Bug#41613: http://bugs.mysql.com/bug.php?id=41613,

Bug#51089: http://bugs.mysql.com/bug.php?id=51089)

* EXPLAIN EXTENDED crashed trying to resolve references to freed

temporary table columns for GROUP_CONCAT() ORDER BY arguments.

(Bug#52397: http://bugs.mysql.com/bug.php?id=52397)

* For InnoDB Plugin, bit fields were causing problems with

concurrency on SMP systems because of word-packing issues.

(Bug#52360: http://bugs.mysql.com/bug.php?id=52360)

* The optimizer could attempt to evaluate the WHERE clause

before any rows had been read, resulting in a server crash.

(Bug#52177: http://bugs.mysql.com/bug.php?id=52177)

* For LDML-defined collations, some data structures were not

initialized properly to enable UPPER() and LOWER() to work

correctly. (Bug#51976: http://bugs.mysql.com/bug.php?id=51976)

* On Windows, LOAD_FILE() could cause a crash for some

pathnames. (Bug#51893: http://bugs.mysql.com/bug.php?id=51893)

* Invalid memory reads occurred for HANDLER … READ NEXT after

a failed HANDLER … READ FIRST.

(Bug#51877: http://bugs.mysql.com/bug.php?id=51877)

* After TRUNCATE TABLE of a MyISAM table, subsequent queries

could crash the server if myisam_use_mmap was enabled.

(Bug#51868: http://bugs.mysql.com/bug.php?id=51868)

* If myisam_sort_buffer_size was set to a small value, table

repair for MyISAM tables with FULLTEXT indexes could crash the

server. (Bug#51866: http://bugs.mysql.com/bug.php?id=51866)

* In LOAD DATA INFILE, using a SET clause to set a column equal

to itself caused a server crash.

(Bug#51850: http://bugs.mysql.com/bug.php?id=51850)

* A problem with equality propagation optimization for prepared

statements and stored procedures caused a server crash upon

re-execution of the prepared statement or stored procedure.

(Bug#51650: http://bugs.mysql.com/bug.php?id=51650)

See also Bug#8115: http://bugs.mysql.com/bug.php?id=8115,

Bug#8849: http://bugs.mysql.com/bug.php?id=8849.

* The optimizer performed an incorrect join type when COALESCE()

appeared within an IN() operation.

(Bug#51598: http://bugs.mysql.com/bug.php?id=51598)

* The server crashed when the optimizer attempted to determine

constant tables but a table storage engine did not support

exact record count.

(Bug#51494: http://bugs.mysql.com/bug.php?id=51494)

* The server could crash populating the

INFORMATION_SCHEMA.PROCESSLIST table due to lack of mutex

protection.

(Bug#51377: http://bugs.mysql.com/bug.php?id=51377)

* Use of HANDLER statements with tables that had spatial indexes

caused a server crash.

(Bug#51357: http://bugs.mysql.com/bug.php?id=51357)

* With an XA transaction active, SET autocommit = 1 could cause

side effects such as memory corruption or a server crash.

(Bug#51342: http://bugs.mysql.com/bug.php?id=51342)

* Following a bulk insert into a MyISAM table, if MyISAM failed

to build indexes using repair by sort, data file corruption

could occur.

(Bug#51307: http://bugs.mysql.com/bug.php?id=51307)

* CHECKSUM TABLE could compute the checksum for BIT columns

incorrectly.

(Bug#51304: http://bugs.mysql.com/bug.php?id=51304)

* A HAVING clause on a joined table in some cases failed to

eliminate rows which should have been excluded from the result

set. (Bug#51242: http://bugs.mysql.com/bug.php?id=51242)

* The type inference used for view columns caused some columns

in views to be handled as the wrong type, as compared to the

same columns in base tables. DATE columns in base tables were

treated as TIME columns in views, and base table TIME columns

as view DATETIME columns.

(Bug#50918: http://bugs.mysql.com/bug.php?id=50918)

* The YEAR values 2000 and 0000 could be treated as equal.

(Bug#49910: http://bugs.mysql.com/bug.php?id=49910)

* Performing a single in-place ALTER TABLE containing ADD INDEX

and DROP INDEX options that used the same index name could

result in a corrupt table definition file. Now such ALTER

TABLE statements are no longer performed in place.

(Bug#49838: http://bugs.mysql.com/bug.php?id=49838)

* mysql_upgrade did not detect when CSV log tables incorrectly

contained columns that could be NULL. Now these columns are

altered to be NOT NULL.

(Bug#49823: http://bugs.mysql.com/bug.php?id=49823)

* If a stored function contained a RETURN statement with an ENUM

value in the ucs2 character set, SHOW CREATE FUNCTION and

SELECT DTD_IDENTIFIER FROM INFORMATION_SCHEMA.ROUTINES

returned incorrect values.

(Bug#48766: http://bugs.mysql.com/bug.php?id=48766)

* The server crashed when it could not determine the best

execution plan for queries involving outer joins with

nondeterministic ON clauses such as the ones containing the

RAND() function, a user-defined function, or a NOT

DETERMINISTIC stored function.

(Bug#48483: http://bugs.mysql.com/bug.php?id=48483)

* A query that read from a derived table (of the form SELECT …

FROM (SELECT …)) produced incorrect results when the

following conditions were present:

+ The table subquery contained a derived query ((SELECT …

) AS column).

+ The derived query could potentially produce zero rows or

a single NULL (that is, no rows matched, or the query

used an aggregate function such as SUM() running over

zero rows).

+ The table subquery joined at least two tables.

+ The join condition involved an index.

(Bug#47904: http://bugs.mysql.com/bug.php?id=47904)

* The optimization to read MIN() or MAX() values from an index

did not properly handle comparisons with NULL values. This

could produce incorrect results for MIN() or MAX()when the

WHERE clause tested a NOT NULL column for NULL.

(Bug#47762: http://bugs.mysql.com/bug.php?id=47762)

* Killing a query during the optimization phase of a subquery

could cause a server crash.

(Bug#47761: http://bugs.mysql.com/bug.php?id=47761)

* The query shown by EXPLAIN EXTENDED plus SHOW WARNINGS could

produce results different from the original query.

(Bug#47669: http://bugs.mysql.com/bug.php?id=47669)

* Renaming a column of an InnoDB table caused the server to go

out of sync with the InnoDB data dictionary.

(Bug#47621: http://bugs.mysql.com/bug.php?id=47621)

* MyISAM could write uninitialized data to new index pages. Now

zeros are written to unused bytes in the pages.

(Bug#47598: http://bugs.mysql.com/bug.php?id=47598)

* Setting myisam_repair_threads larger than 1 could result in

the cardinality for all indexes of a MyISAM table being set to

1 after parallel index repair.

(Bug#47444: http://bugs.mysql.com/bug.php?id=47444)

* In debug builds, if the listed columns in the view definition

of the table used in an INSERT … SELECT statement

mismatched, an assertion was raised in the query cache

invalidation code following the failing statement.

(Bug#46615: http://bugs.mysql.com/bug.php?id=46615)

* For a query that selected from a view and used an alias for

the view, the metadata used the alias name rather than the

view name in the MYSQL_FIELD.table member.

(Bug#41788: http://bugs.mysql.com/bug.php?id=41788)

* mysql_upgrade did not create temporary files properly.

(Bug#41057: http://bugs.mysql.com/bug.php?id=41057)

* It was possible for DROP TABLE of one MyISAM table to remove

the data and index files of a different MyISAM table.

(Bug#40980: http://bugs.mysql.com/bug.php?id=40980)

* If the arguments to a CONCAT() call included a local routine

variable, selecting the return value into a user variable

could produce an incorrect result.

(Bug#40625: http://bugs.mysql.com/bug.php?id=40625)

* SHOW CREATE VIEW returned invalid SQL if the definition

contained a SELECT ‘string’ statement where the string was

longer than the maximum length of a column name, due to the

fact that this text was also used as an alias (in the AS

clause).

Because not all names retrieved from arbitrary SELECT

statements can be used as view column names due to length and

format restrictions, the server now checks the conformity of

automatically generated column names and rewrites according to

a predefined format any names that are not acceptable as view

column names before storing the final view definition on disk.

In such cases, the name is now rewritten as Name_exp_pos,

where pos is the position of the column. To avoid this

conversion scheme, define explicit, valid names for view

columns using the column_list clause of the CREATE VIEW

statement.

As part of this fix, aliases are now generated only for

top-level statements.

(Bug#40277: http://bugs.mysql.com/bug.php?id=40277)

* While looking for the shortest index for a covering index

scan, the optimizer ignored that a clustered primary key read

the entire table.

(Bug#39653: http://bugs.mysql.com/bug.php?id=39653)

* mysqlbinlog had a memory leak in its option-processing code.

(Bug#38468: http://bugs.mysql.com/bug.php?id=38468)

* The test for readline during configuration failed when trying

to build MySQL in a directory other than the source tree root.

(Bug#35250: http://bugs.mysql.com/bug.php?id=35250)

For an overview of what’s new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.45 on new servers or upgrading to MySQL 5.1.45 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from http://dev.mysql.com/downloads/

For information on open issues in MySQL 5.1, please see the errata
list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html

Changes in MySQL 5.1.45

InnoDB Plugin Notes:

* This release includes InnoDB Plugin 1.0.6. This version is
considered of Release Candidate (RC) quality.
In this release, the InnoDB Plugin is included in source and
binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,
x86_64, ia64), and generic Linux RPM packages. It also does
not work for FreeBSD 6 and HP-UX or for Linux on generic ia64.

Functionality added or changed:

* mysqltest has a new –max-connections option to set a higher
number of maximum allowed server connections than the default
128. This option can also be passed via mysql-test-run.pl.
(Bug#51135: http://bugs.mysql.com/bug.php?id=51135)

* mysql-test-run.pl has a new –portbase option and a
corresponding MTR_PORT_BASE environment variable for setting
the port range, as an alternative to the existing
–build-thread option.
(Bug#50182: http://bugs.mysql.com/bug.php?id=50182)

* mysql-test-run.pl has a new –gprof option that runs the
server through the gprof profiler, much the same way the
currently supported –gcov option runs it through gcov.
(Bug#49345: http://bugs.mysql.com/bug.php?id=49345)

* mysqltest has a new lowercase_result command that converts the
output of the next statement to lowercase. This is useful for
test cases where the lettercase may vary between platforms.
(Bug#48863: http://bugs.mysql.com/bug.php?id=48863)

* mysqltest has a new remove_files_wildcard command that removes
files matching a pattern from a directory.
(Bug#39774: http://bugs.mysql.com/bug.php?id=39774)

Bugs fixed:

* Partitioning: Attempting to drop a partitioned table from one
connection while waiting for the completion of an ALTER TABLE
that had been issued from a different connection, and that
changed the storage engine used by the table, could cause the
server to crash.
(Bug#42438: http://bugs.mysql.com/bug.php?id=42438)

* Replication: Adding an index to a table on the master caused
the slave to stop logging slow queries to the slow query log.
(Bug#50620: http://bugs.mysql.com/bug.php?id=50620)

* Replication: Queries which were written to the slow query log
on the master were not written to the slow query log on the
slave. (Bug#23300: http://bugs.mysql.com/bug.php?id=23300)
See also Bug#48632: http://bugs.mysql.com/bug.php?id=48632.

* mysqld_multi failed due to a syntax error in the script.
(Bug#51468: http://bugs.mysql.com/bug.php?id=51468)

* Referring to a subquery result in a HAVING clause could
produce incorrect results.
(Bug#50995: http://bugs.mysql.com/bug.php?id=50995)

* Use of filesort plus the join cache normally is preferred to a
full index scan. But it was used even if the index is
clustered, in which case, the clustered index scan can be
faster. (Bug#50843: http://bugs.mysql.com/bug.php?id=50843)

* For debug builds, SHOW BINARY LOGS caused an assertion to be
raised if binary logging was not enabled.
(Bug#50780: http://bugs.mysql.com/bug.php?id=50780)

* Incorrect handling of BIT columns in temporary tables could
lead to spurious duplicate-key errors.
(Bug#50591: http://bugs.mysql.com/bug.php?id=50591)

* Full-text queries that used the truncation operator (*) could
enter an infinite loop.
(Bug#50351: http://bugs.mysql.com/bug.php?id=50351)

* mysqltest no longer lets you execute an SQL statement on a
connection after doing a send command, unless you do a reap
first. This was previously accepted but could produce
unpredictable results.
(Bug#49269: http://bugs.mysql.com/bug.php?id=49269)

* For debug builds on Windows, warnings about incorrect use of
debugging directives were written to the error log. The
directives were rewritten to eliminate these messages.
(Bug#49025: http://bugs.mysql.com/bug.php?id=49025)

* Building MySQL on Fedora Core 12 64-bit failed, due to errors
in comp_err.
(Bug#48864: http://bugs.mysql.com/bug.php?id=48864)

* An ARZ file missing from the database directory caused the
server to crash.
(Bug#48757: http://bugs.mysql.com/bug.php?id=48757)

* Slow CALL statements were not always logged to the slow query
log because execution time for multiple-statement stored
procedures was assessed incorrectly.
(Bug#47905: http://bugs.mysql.com/bug.php?id=47905)

* Failure to open a view with a nonexistent DEFINER was
improperly handled and the server would crash later attempting
to lock the view.
(Bug#47734: http://bugs.mysql.com/bug.php?id=47734)

* If EXPLAIN encountered an error in the query, a memory leak
occurred. (Bug#45989: http://bugs.mysql.com/bug.php?id=45989)

* Grouping by a subquery in a query with a DISTINCT aggregate
function led to incorrect and unordered grouping values.
(Bug#45640: http://bugs.mysql.com/bug.php?id=45640)

* Propagation of a large unsigned numeric constant in WHERE
expressions could lead to incorrect results. This also
affected EXPLAIN EXTENDED, which printed incorrect numeric
constants in such transformed WHERE expressions.
(Bug#45360: http://bugs.mysql.com/bug.php?id=45360)

* Valgrind warnings about uninitialized variables in optimizer
code were silenced.
(Bug#45195: http://bugs.mysql.com/bug.php?id=45195)

* flush_cache_records() did not correctly check for errors that
should cause statement execution to stop, leading to a server
crash. (Bug#39022: http://bugs.mysql.com/bug.php?id=39022)

* When building MySQL when using a different target directory
(for example using the VPATH environment variable), the build
of the embedded readline component would fail.
(Bug#35250: http://bugs.mysql.com/bug.php?id=35250)

* INSERT INTO … VALUES(DEFAULT) failed to insert the correct
value for ENUM columns. For MyISAM tables, an empty value was
inserted. For CSV tables, the table became corrupt.
(Bug#33717: http://bugs.mysql.com/bug.php?id=33717)

For an overview of what’s new in MySQL 5.1, please see  http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.44 on new servers or upgrading to MySQL 5.1.44 from previous MySQL releases, please see  http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of platforms from  http://dev.mysql.com/downloads/

For information on open issues in MySQL 5.1, please see the errata list at  http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1.  It may also be viewed online at  http://dev.mysql.com/doc/refman/5.1/en/news-5-1-44.html

Changes in MySQL 5.1.44

InnoDB Plugin Notes:

* This release includes InnoDB Plugin 1.0.6. This version is considered of Release Candidate (RC) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,

x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64.

Functionality added or changed:

* Replication: Introduced the –binlog-direct-non-transactional-updates server option. This option causes updates using the statement-based logging format to tables using non-transactional engines to be written directly to the binary log, rather than to the transaction cache.

Before using this option, be certain that you have no dependencies between transactional and non-transactional tables. A statement that both selects from an InnoDB table and inserts into a MyISAM table is an example of such a dependency. For more information, see Section 16.1.3.4,

“Binary Log Options and Variables.”

(Bug#46364: http://bugs.mysql.com/bug.php?id=46364)

See also Bug#28976: http://bugs.mysql.com/bug.php?id=28976,

Bug#40116: http://bugs.mysql.com/bug.php?id=40116.

Bugs fixed:

* Partitioning: When an ALTER TABLE … REORGANIZE PARTITION statement on an InnoDB table failed due to innodb_lock_wait_timeout expiring while waiting for a lock, InnoDB did not clean up any temporary files or tables which it had created. Attempting to reissue the ALTER TABLE statement following the timeout could lead to storage engine errors, or possibly a crash of the server.

(Bug#47343: http://bugs.mysql.com/bug.php?id=47343)

* Replication: In some cases, inserting into a table with many columns could cause the binary log to become corrupted.

(Bug#50018: http://bugs.mysql.com/bug.php?id=50018)

See also Bug#42749: http://bugs.mysql.com/bug.php?id=42749.

* Replication: When using row-based replication, setting a BIT or CHAR column of a MyISAM table to NULL, then trying to delete from the table, caused the slave to fail with the error Can’t find record in table.

(Bug#49481: http://bugs.mysql.com/bug.php?id=49481,

Bug#49482: http://bugs.mysql.com/bug.php?id=49482)

* Replication: When logging in row-based mode, DDL statements are actually logged as statements; however, statements that affected temporary tables and followed DDL statements failed to reset the binary log format to ROW, with the result that these statements were logged using the statement-based format. Now the state of binlog_format is restored after a DDL statement has been written to the binary log.

(Bug#49132: http://bugs.mysql.com/bug.php?id=49132)

* Replication: When using row-based logging, the statement CREATE TABLE t IF NOT EXIST … SELECT was logged as CREATE TEMPORARY TABLE t IF NOT EXIST … SELECT when t already existed as a temporary table. This was caused by the fact that the temporary table was opened and the results of the SELECT were inserted into it when a temporary table existed and had the same name.

Now, when this statement is executed, t is created as a base table, the results of the SELECT are inserted into it — even if there already exists a temporary table having the same name — and the statement is logged correctly.

(Bug#47418: http://bugs.mysql.com/bug.php?id=47418)

See also Bug#47442: http://bugs.mysql.com/bug.php?id=47442.

* Replication: Due to a change in the size of event representations in the binary log, when replicating from a MySQL 4.1 master to a slave running MySQL 5.0.60 or later, the START SLAVE UNTIL statement did not function correctly, stopping at the wrong position in the log. Now the slave detects that the master is using the older version of the binary log format, and corrects for the difference in event size, so that the slave stops in the correct position.

(Bug#47142: http://bugs.mysql.com/bug.php?id=47142)

* The SSL certificates in the test suite were about to expire. They have been updated with expiration dates in the year 2015.

(Bug#50642: http://bugs.mysql.com/bug.php?id=50642)

* The printstack function does not exist on Solaris 8 or earlier, which would lead to a compilation failure.

(Bug#50409: http://bugs.mysql.com/bug.php?id=50409)

* A user could see tables in INFORMATION_SCHEMA.TABLES without appropriate privileges for them.

(Bug#50276: http://bugs.mysql.com/bug.php?id=50276)

* Debug output for join structures was garbled.

(Bug#50271: http://bugs.mysql.com/bug.php?id=50271)

* The filesort sorting method applied to a CHAR(0) column could lead to a server crash.

(Bug#49897: http://bugs.mysql.com/bug.php?id=49897)

* sql_buffer_result had an effect on non-SELECT statements, contrary to the documentation.

(Bug#49552: http://bugs.mysql.com/bug.php?id=49552)

* In some cases a subquery need not be evaluated because it returns only aggregate values that can be calculated from table metadata. This sometimes was not handled by the enclosing subquery, resulting in a server crash.

(Bug#49512: http://bugs.mysql.com/bug.php?id=49512)

* The method for comparing INFORMATION_SCHEMA names and database names was nonoptimal and an improvement was made: When the database name length is already known, a length check is made

first and content comparison skipped if the lengths are unequal.

(Bug#49501: http://bugs.mysql.com/bug.php?id=49501)

* The MD5() and SHA1() functions had excessive overhead for short strings.

(Bug#49491: http://bugs.mysql.com/bug.php?id=49491)

* Mixing full-text searches and row expressions caused a crash.

(Bug#49445: http://bugs.mysql.com/bug.php?id=49445)

* Creating or dropping a table with 1023 transactions active caused an assertion failure.

(Bug#49238: http://bugs.mysql.com/bug.php?id=49238)

* mysql-test-run.pl now recognizes the MTR_TESTCASE_TIMEOUT, MTR_SUITE_TIMEOUT, MTR_SHUTDOWN_TIMEOUT, and MTR_START_TIMEOUT environment variables. If they are set, their values are used to set the –testcase-timeout, –suite-timeout, –shutdown-timeout, and –start-timeout options, respectively.

(Bug#49210: http://bugs.mysql.com/bug.php?id=49210)

MySQL 5.1.42 is recommended for use on production systems.

For an overview of what’s new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.42 on new servers or upgrading to MySQL 5.1.42 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/

For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-42.html

Changes in MySQL 5.1.42

Release availability:

MySQL Server 5.1 is available on the following new platforms starting with the 5.1.42 release:

+ Mac OS X 10.6 x86/x64

+ HP-UX 11.31 IA64

+ SLES 11 x86/x64

Important Change to Replication:

The following functions have been marked unsafe for statement-based replication:

+ GET_LOCK()

+ IS_FREE_LOCK()

+ IS_USED_LOCK()

+ MASTER_POS_WAIT()

+ RELEASE_LOCK()

+ SLEEP()

+ SYSDATE()

+ VERSION()

None of the functions just listed are guaranteed to replicate correctly when using the statement-based format, because they can produce different results on the master and the slave. The use of any of these functions while binlog_format is set to STATEMENT is logged with the warning, Statement is not safe to log in statement format. When binlog_format is set to MIXED, the binary logging format is automatically switched to the row-based format whenever one of these functions is used. (Bug#47995: http://bugs.mysql.com/bug.php?id=47995) InnoDB

Plugin Notes:

* InnoDB Plugin has been upgraded to version 1.0.6. This version is considered of Release Candidate (RC) quality. The InnoDB Plugin Change History (http://www.innodb.com/doc/innodb_plugin-1.0/innodb-changes.html) may contain information in addition to those changes reported here. Bugs fixed:

* Performance: When the query cache is fragmented, the size of the free block lists in the memory bins grows, which causes query cache invalidation to become slow. There is now a 50ms timeout for a SELECT statement waiting for the query cache lock. If the timeout expires, the statement executes without using the query cache. (Bug#39253: http://bugs.mysql.com/bug.php?id=39253)

* Partitioning: In some cases, it was not possible to add a new column to a table that had subpartitions. (Bug#48276: http://bugs.mysql.com/bug.php?id=48276)

* Partitioning: SELECT COUNT(*) from a partitioned table failed when using the ONLY_FULL_GROUP_BY SQL mode. (Bug#46923: http://bugs.mysql.com/bug.php?id=46923) This regression was introduced by Bug#45807: http://bugs.mysql.com/bug.php?id=45807.

* Partitioning: SUBPARTITION BY KEY failed with DEFAULT CHARSET=utf8. (Bug#45904: http://bugs.mysql.com/bug.php?id=45904)

* Replication: When using row-based logging, TRUNCATE TABLE was written to the binary log even if the affected table was temporary, causing replication to fail. (Bug#48350: http://bugs.mysql.com/bug.php?id=48350)

* Replication: Replicating TEXT or VARCHAR columns declared as NULL on the master but NOT NULL on the slave caused the slave to crash. (Bug#43789: http://bugs.mysql.com/bug.php?id=43789) See also Bug#38850: http://bugs.mysql.com/bug.php?id=38850, Bug#43783: http://bugs.mysql.com/bug.php?id=43783, Bug#43785: http://bugs.mysql.com/bug.php?id=43785, Bug#47741: http://bugs.mysql.com/bug.php?id=47741, Bug#48091: http://bugs.mysql.com/bug.php?id=48091.

* InnoDB did not reset table AUTO_INCREMENT values to the last used values after a server restart. (Bug#49032: http://bugs.mysql.com/bug.php?id=49032)

* Privileges for stored routines were ignored for mixed-case routine names. (Bug#48872: http://bugs.mysql.com/bug.php?id=48872) See also Bug#41049: http://bugs.mysql.com/bug.php?id=41049.

* Building MySQL on Fedora Core 12 64-bit would due to errors in comp_err. (Bug#48864: http://bugs.mysql.com/bug.php?id=48864)

* Concurrent ALTER TABLE operations on an InnoDB table could raise an assertion. (Bug#48782: http://bugs.mysql.com/bug.php?id=48782)

* During query execution, ranges could be merged incorrectly for OR operations and return an incorrect result. (Bug#48665: http://bugs.mysql.com/bug.php?id=48665)

* The InnoDB Table Monitor reported the FLOAT and DOUBLE data types incorrectly. (Bug#48526: http://bugs.mysql.com/bug.php?id=48526)

* With row-based binary logging, the server crashed for statements of the form CREATE TABLE IF NOT EXISTS existing_view LIKE temporary_table. This occurred because the server handled the existing view as a table when logging the statement. (Bug#48506: http://bugs.mysql.com/bug.php?id=48506)

* DISTINCT was ignored for queries with GROUP BY WITH ROLLUP and only const tables. (Bug#48475: http://bugs.mysql.com/bug.php?id=48475)

* Loose index scan was inappropriately chosen for some WHERE conditions. (Bug#48472: http://bugs.mysql.com/bug.php?id=48472)

* A bad typecast could cause query execution to allocate large amounts of memory. (Bug#48458: http://bugs.mysql.com/bug.php?id=48458)

* On Windows, InnoDB could not be built as a statically linked library. (Bug#48317: http://bugs.mysql.com/bug.php?id=48317)

* When running mysql_secure_installation, the command would fail if the root password contained multiple spaces, \, # or quote characters. (Bug#48031: http://bugs.mysql.com/bug.php?id=48031)

* MATCH IN BOOLEAN MODE searches could return too many results inside a subquery. (Bug#47930: http://bugs.mysql.com/bug.php?id=47930)

* Connecting to a 4.1.x server from a 5.1.x or higher mysql client resulted in a memory-free error when disconnecting. (Bug#47655: http://bugs.mysql.com/bug.php?id=47655)

* Assignment of a system variable sharing the same base name as a declared stored program variable in the same context could lead to a crash. (Bug#47627: http://bugs.mysql.com/bug.php?id=47627)

* The innodb_file_format_check system variable could not be set at runtime to DEFAULT or to the value of a user-defined variable. (Bug#47167: http://bugs.mysql.com/bug.php?id=47167)

* Valgrind errors for InnoDB Plugin were corrected. (Bug#45992: http://bugs.mysql.com/bug.php?id=45992, Bug#46656: http://bugs.mysql.com/bug.php?id=46656)

* On 64-bit systems, –skip-innodb did not skip InnoDB startup. (Bug#46043: http://bugs.mysql.com/bug.php?id=46043)

* Truncation of DECIMAL values could lead to assertion failures; for example, when deducing the type of a table column from a literal DECIMAL value. (Bug#45261: http://bugs.mysql.com/bug.php?id=45261) See also Bug#48370: http://bugs.mysql.com/bug.php?id=48370.

* For YEAR(2) values, MIN(), MAX(), and comparisons could yield incorrect results. (Bug#43668: http://bugs.mysql.com/bug.php?id=43668)

* The server could crash when attempting to access a non-conformant mysql.proc system table. For example, the server could crash when invoking stored procedure-related statements after an upgrade from MySQL 5.0 to 5.1 without running mysql_upgrade. (Bug#41726: http://bugs.mysql.com/bug.php?id=41726)

* When running mysql_secure_installation on Windows, the command would fail to load a required module, Term::ReadKey, which was required for correct operation. (Bug#35106: http://bugs.mysql.com/bug.php?id=35106)

* If the –log-bin server option was set to a directory name with a trailing component separator character, the basename of the binary log files was empty so that the created files were named .000001 and .index. The same thing occurred with the –log-bin-index, –relay-log, and –relay-log-index options. Now the server reports and error and exits. (Bug#34739: http://bugs.mysql.com/bug.php?id=34739)

* On some Windows systems, InnoDB could report Operating system error number 995 in a file operation due to transient driver or hardware problems. InnoDB now retries the operation and adds Retry attempt is made to the error message. (Bug#3139: http://bugs.mysql.com/bug.php?id=3139)

* Replication: When using row-based format, replication failed with the error Could not execute Write_rows event on table …; Field ‘…’ doesn’t have a default value when an INSERT was made on the master without specifying a value for a column having no default, even if strict server SQL mode was not in use and the statement would otherwise have succeeded on the master. Now the SQL mode is checked, and the statement is replicated unless strict mode is in effect. For more information, see Section 5.1.8, “Server SQL Modes.” (Bug#38173: http://bugs.mysql.com/bug.php?id=38173) See also Bug#38262: http://bugs.mysql.com/bug.php?id=38262, Bug#43992: http://bugs.mysql.com/bug.php?id=43992.

* The result of comparison between nullable BIGINT and INT columns was inconsistent. (Bug#49517: http://bugs.mysql.com/bug.php?id=49517)

* Incorrect cache initialization prevented storage of converted constant values and could produce incorrect comparison results. (Bug#49489: http://bugs.mysql.com/bug.php?id=49489)

* Comparisons involving YEAR values could produce incorrect results. (Bug#49480: http://bugs.mysql.com/bug.php?id=49480) See also Bug#43668: http://bugs.mysql.com/bug.php?id=43668.

* If a query involving a table was terminated with KILL, a subsequent SHOW CREATE TABLE for that table caused a server crash. (Bug#48985: http://bugs.mysql.com/bug.php?id=48985)

* If the InnoDB tablespace was configured with too small a value, the server could crash and corrupt the tablespace. (Bug#48469: http://bugs.mysql.com/bug.php?id=48469)

* Parts of the range optimizer could be initialized incorrectly, resulting in Valgrind errors. (Bug#48459: http://bugs.mysql.com/bug.php?id=48459)

* On Windows, InnoDB could not be built as a statically linked library. (Bug#48317: http://bugs.mysql.com/bug.php?id=48317)

* mysql_secure_installation did not work on Solaris. (Bug#48086: http://bugs.mysql.com/bug.php?id=48086)

* Using REPLACE to update a previously inserted negative value in an AUTO_INCREMENT coumn in an InnoDB table caused the table auto-increment value to be updated to 2147483647. (Bug#47720: http://bugs.mysql.com/bug.php?id=47720)

* If a session held a global read lock acquired with FLUSH TABLES WITH READ LOCK, a lock for one table acquired with LOCK TABLES, and issued an INSERT DELAYED statement for another table, deadlock could occur. (Bug#47682: http://bugs.mysql.com/bug.php?id=47682)

* The mysql client status command displayed an incorrect value for the server character set. (Bug#47671: http://bugs.mysql.com/bug.php?id=47671)

* After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation that contains ARCHIVE tables, accessing those tables caused the server to crash, even if you had run mysql_upgrade or CHECK TABLE … FOR UPGRADE. To work around this problem, use mysqldump to dump all ARCHIVE tables before upgrading, and reload them into MySQL 5.1 after upgrading. The same problem occurs for binary downgrades from MySQL 5.1 to 5.0. (Bug#47012: http://bugs.mysql.com/bug.php?id=47012)

* The IGNORE clause on a DELETE statement masked an SQL statement error that occurred during trigger processing. (Bug#46425: http://bugs.mysql.com/bug.php?id=46425)

* The return value was not checked for some my_hash_insert() calls. (Bug#45613: http://bugs.mysql.com/bug.php?id=45613)

* Use of InnoDB monitoring (SHOW ENGINE INNODB STATUS or one of the InnoDB Monitor tables) could cause a server crash due to invalid access to a shared variable in a concurrent environment. This is a further fix for a regression introduced in MySQL 5.1.38 to the original fix in MySQL 5.1.31. (Bug#38883: http://bugs.mysql.com/bug.php?id=38883)

* If a comparison involved a constant value that required type conversion, the converted value might not be cached, resulting in repeated conversion and poorer performance. (Bug#34384: http://bugs.mysql.com/bug.php?id=34384)

* Using the SHOW ENGINE INNODB STATUS statement when using partitions in InnoDB tables caused Invalid (old?) table or database name errors to be logged. (Bug#32430: http://bugs.mysql.com/bug.php?id=32430)

* The Mac OS X 10.6 MySQL preference panel now contains x86 64-bit binaries. (Bug#46935: http://bugs.mysql.com/bug.php?id=46935)