Marketgrid Consulting Blog » MySQL Community Server

MySQL Community Server 5.5.15

Phil Smith — Fri, 29 Jul 2011 14:58:28 +0000

MySQL 5.5.15 is a new version of the 5.5 production release of the world’s most popular open source database. MySQL 5.5.15 is recommended for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In

addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various Windows specific features and improvements

- Higher availability, with new semi-synchronous replication and Replication Heart Beat

- Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability.

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

Changes in MySQL 5.5.15 (28 July 2011)

Functionality Added or Changed

* The undocumented –all option for perror is deprecated and

will be removed in MySQL 5.6.

Bugs Fixed

* InnoDB Storage Engine: A failed CREATE INDEX operation for an

InnoDB table could result in some memory being allocated but

not freed. This memory leak could affect tables created with

the ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED setting. (Bug

#12699505)

* Partitioning: Auto-increment columns of partitioned tables

were checked even when they were not being written to. In

debug builds, this could lead to a server crash. (Bug

#11765667, Bug #58655)

* Partitioning: The UNIX_TIMESTAMP() function was not treated as

a monotonic function for purposes of partition pruning. (Bug

#11746819, Bug #28928)

* Compiling the server with maintainer mode enabled failed for

gcc 4.6 or higher. (Bug #12727287)

* The option-parsing code for empty strings leaked memory. (Bug

#12589928)

* Previously, an inappropriate error message was produced if a

multiple-table update for an InnoDB table with a clustered

primary key would update a table through multiple aliases, and

perform an update that may physically move the row in at least

one of these aliases. Now the error message is: Primary

key/partition key update is not permitted since the table is

updated both as ‘tbl_name1′ and ‘tbl_name2′ (Bug #11882110)

MySQL Community Server 5.5.13

Phil Smith — Wed, 01 Jun 2011 08:40:27 +0000

MySQL 5.5.13 is a new version of the 5.5 production release of the

world’s most popular open source database. MySQL 5.5.13 is recommended

for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the

performance and scalability of the MySQL Database, taking advantage of

the latest multi-CPU and multi-core hardware and operating systems. In

addition, with release 5.5, InnoDB is now the default storage engine for

the MySQL Database, delivering ACID transactions, referential integrity

and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various Windows specific features and improvements

- Higher availability, with new semi-synchronous replication and Replication Heart Beat

- Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability.

Changes in MySQL 5.5.13 :

Note:

Very old (MySQL 4.0) clients are not working temporarily due to a

problem discovered after the release of MySQL 5.5.12. We are

looking at fixing the problem.

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)

* InnoDB Storage Engine: Similar problem to the foreign key

error in bug #11831040 / 60196 / 60909, but with a different

root cause and occurring on Mac OS X. With the setting

lower_case_table_names=2, inserts into InnoDB tables covered

by foreign key constraints could fail after a server restart.

* Partitioning: The internal get_partition_set() function did

not take into account the possibility that a key specification

could be NULL in some cases. (Bug #12380149)

* Partitioning: When executing a row-ordered retrieval index

merge, the partitioning handler used memory from that

allocated for the table, rather than that allocated to the

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

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

* Replication: A spurious error malformed binlog: it does not

contain any Format_description_log_event… was generated 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. However, there is

nothing unsafe about not printing the format description log

event, so 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)

* Assignments to NEW.var_name within triggers, where var_name

had a BLOB or TEXT type, were not properly handled and

produced incorrect results. (Bug #12362125)

* XA COMMIT could fail to clean up the error state if it

discovered that the current XA transaction had to be rolled

back. Consequently, the next XA transaction could raise an

assertion when it checked for proper cleanup of the previous

transaction. (Bug #12352846)

* An internal client macro reference was removed from the

client_plugin.h header file. This reference made the file

unusable. (Bug #60746, Bug #12325444)

* The server consumed memory for repeated invocation of some

stored procedures, which was not released until the connection

terminated. (Bug #60025, Bug #11848763)

* The server did not check for certain invalid out of order

sequences of XA statements, and these sequences raised an

assertion. (Bug #59936, Bug #11766752, Bug #12348348)

* With the conversion from GNU autotools to CMake for

configuring MySQL, the USE_SYMDIR preprocessor symbol was

omitted. This caused failure of symbolic links (described at

Section 7.11.3.1, “Using Symbolic Links”). (Bug #59408, Bug

#11766320)

* 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)

* Internal Performance Schema header files were unnecessarily

installed publicly. (Bug #53281)

* 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)

* With DISTINCT CONCAT(col,…) returned incorrect results when

the arguments to CONCAT() were columns with an integer data

type declared with a display width narrower than the values in

the column. (For example, if an INT(1) column contain 1111.)

(Bug #4082)

MySQL Community Server 5.6.2 (Bugs)

Phil Smith — Tue, 12 Apr 2011 11:13:31 +0000

Bugs fixed:

* Performance: InnoDB Storage Engine: An UPDATE statement for an

InnoDB table could be slower than necessary if it changed a

column covered by a prefix index, but did not change the

prefix portion of the value. The fix improves performance for

InnoDB 1.1 in MySQL 5.5 and higher, and the InnoDB Plugin for

MySQL 5.1. (Bug #58912, Bug #11765900)

* Incompatible Change: When auto_increment_increment is greater

than one, values generated by a bulk insert that reaches the

maximum column value could wrap around rather producing an

overflow error.

As a consequence of the fix, it is no longer possible for an

auto-generated value to be equal to the maximum BIGINT

UNSIGNED value. It is still possible to store that value

manually, if the column can accept it. (Bug #39828, Bug

#11749800)

* Important Change: Partitioning: Date and time functions used

as partitioning functions now have the types of their operands

checked; use of a value of the wrong type is now disallowed in

such cases. In addition, EXTRACT(WEEK FROM col), where col is

a DATE or DATETIME column, is now disallowed altogether

because its return value depends on the value of the

default_week_format system variable. (Bug #54483, Bug

#11761948)

MySQL Community Server 5.6.2

Phil Smith — Tue, 12 Apr 2011 09:13:15 +0000

MySQL Server 5.6.2 (Milestone Release) is a new version of the world’s most popular open source database.

The new features in these releases are of beta quality. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.

Note that 5.6.2 includes all features in MySQL 5.5. For an overview of

what’s new in MySQL 5.6, please see the section “What Is New in MySQL

5.6″ below, or view it online at http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html

For information on installing MySQL 5.6.2 on new servers, please see the

MySQL installation documentation at http://dev.mysql.com/doc/refman/5.6/en/installing.html

For upgrading from previous MySQL releases, please see the important

upgrade considerations at http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html

Please note that *downgrading* from these releases to a previous release

series is not supported.

MySQL Server 5.6 is available in source and binary form for a number of

platforms from the “Development Releases” selection of the download

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

The list of all “Bugs Fixed” for 5.6.2 may also be viewed online at

http://dev.mysql.com/doc/refman/5.6/en/news-5-6-2.html

D.1.2. Changes in MySQL 5.6.2 (11 April 2011)

Explicit Partition Selection

* Partitioning: It is now possible to select one or more

partitions or subpartitions when querying from a partitioned

table. In addition, many data modification statements (DELETE,

INSERT, REPLACE, UPDATE, LOAD DATA, and LOAD XML) that act on

partitioned tables also now support explicit partition

selection. For example, assume we have a table named t with

some integer column named c, and t has 4 partitions named p0,

p1, p2, and p3. Then the query SELECT * FROM t PARTITION (p0,

p1) WHERE c < 5 returns rows only in partitions p0 and p1 that

match the WHERE condition, while partitions p2 and p3 are not

checked.

For additional information and examples, see Section 16.5,

“Partition Selection,” as well as the descriptions of the

statements just listed.

Row Image Control

* Replication: Added the binlog_row_image server system

variable, which can be used to enable row image control for

row-based replication. This means that you can potentially

save disk space, network resources, and memory usage by the

MySQL Server by logging only those columns that are required

for uniquely identifying rows, or which are actually changed

on each row, as opposed to logging all columns for each and

every row change event. In addition, you can use a “noblob”

mode where all columns, except for unneeded BLOB or TEXT

columns, are logged.

For more information, see Section 15.1.3.4, “System variables

used with the binary log.” (Bug #47200, Bug #11755426, Bug

#47303, Bug #56917, Bug #11755426, Bug #11755513, Bug

#11764116)

Crash-Safe Binary Log

* Replication: Support for checksums when writing and reading

the binary log is added to the MySQL Server. Writing checksums

into the binary log is disabled by default; it can be enabled

by starting the server with the –binlog-checksum option. To

cause the server to read checksums from the binary log, start

the server with the –master-verify-checksum option. The

–slave-sql-verify-checksum option causes the slave to read

checksums from the relay log.

* Replication: The MySQL Server now records and reads back only

complete events or transactions to and from the binary log. By

default, the server now logs the length of the event as well

as the event itself and uses this information to verify that

the event was written correctly to the log. A master also uses

by default this value to verify events when reading from the

binary log.

If you enable writing of checksums (using the binlog_checksum

system variable), the master can use these instead by enabling

the master_verify_checksum system variable. The slave I/O

thread also verifies events received from the master. You can

cause the slave SQL thread to use checksums (if available) as

well, when reading from the relay log, by enabling the

slave_sql_verify_checksum system variable on the slave.

Slave Log Tables

* Replication: It is now possible to write information about the

slave connection to the master and about the slave’s execution

point within the relay log to tables rather than files.

Logging of master connection information and of slave relay

log information to tables can be done independently of one

another; this is controlled by the –master-info-repository

and –relay-log-info-repository server options. When

–master-info-repository is set to TABLE, connection

information is logged in the slave_master_info table in the

mysql system database. When –relay-log-info-repository is set

to TABLE, relay log information is logged to the

slave_relay_log_info table, also in the mysql database.

Globally Unique Server IDs

* Replication: Implemented globally unique IDs for MySQL

servers. A UUID is now obtained automatically when the MySQL

server starts. The server first checks for a UUID written in

the auto.cnf file (in the server’s data directory), and uses

this UUID if found. Otherwise, the server generates a new UUID

and saves it to this file (and creates the file if it does not

already exist). This UUID is available as the server_uuid

system variable.

MySQL replication masters and slaves know each other’s UUIDs.

The value of a slave’s UUID can be read on the master as the

system variable slave_uuid, as well as in the output of SHOW

SLAVE HOSTS. After a slave is started (with START SLAVE), the

value of the master’s UUID is available on the slave as the

master_uuid system variable, as well as in the output of SHOW

SLAVE STATUS.

For more information, see Section 15.1.3, “Replication and

Binary Logging Options and Variables.” (Bug #33815, Bug

#11747723)

MySQL Community Server 5.5.11

Phil Smith — Thu, 07 Apr 2011 13:31:19 +0000

MySQL 5.5.11 is a new version of the 5.5 production release of the world’s most popular open source database. MySQL 5.5.11 is recommended for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the

performance and scalability of the MySQL Database, taking advantage of

the latest multi-CPU and multi-core hardware and operating systems. In

addition, with release 5.5, InnoDB is now the default storage engine for

the MySQL Database, delivering ACID transactions, referential integrity

and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various Windows specific features and improvements

- Higher availability, with new semi-synchronous replication and Replication Heart Beat

- Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability.

————————————————————————

D.1.2. Changes in MySQL 5.5.11 (07 April 2011):

Functionality added or changed:

* The undocumented SHOW NEW MASTER statement has been removed.

Bugs fixed:

* Partitioning: A problem with a previous fix for poor

performance of INSERT ON DUPLICATE KEY UPDATE statements on

tables having many partitions caused the handler function for

reading a row from a specific index to fail to store the ID of

the partition last used. This caused some statements to fail

with Can’t find record errors. (Bug #59297, Bug #11766232)

* On some systems, debug builds of comp_err.c could fail due to

an uninitialized variable. (Bug #59906, Bug #11766729)

* The server read one byte too many when trying to process an

XML string lacking a closing quote (‘) or double quote (“)

character used as an argument for UpdateXML() or

ExtractValue(). (Bug #59901, Bug #11766725)

MySQL Community Server 5.5.8

Phil Smith — Thu, 16 Dec 2010 08:47:47 +0000

MySQL Database 5.5.8 GA has been released.

The first 5.5 production version of the world’s most popular open source database. MySQL 5.5.8 is recommended for use on production systems.

MySQL 5.5 includes several high-impact changes to address scalability and performance issues in MySQL Database. These changes exploit advances in hardware and CPU design and enable better utilization of existing

hardware. MySQL 5.5 also provides a number of other new enhancements, including:

- InnoDB I/O Subsystem Changes

- Enhanced Solaris Support

- Diagnostic and Monitoring Capabilities

The following section lists the changes in the MySQL source code since

the previous released version of MySQL 5.5.

—-

D.1.1. Changes in MySQL 5.5.8 (03 December 2010)

Configuration Notes:

* MySQL releases are now built on all platforms using CMake

rather than the GNU autotools, so autotools support has been

removed. For instructions on building MySQL with CMake, see

Section 2.11, “Installing MySQL from Source.” Third-party

tools that need to extract the MySQL version number formerly

found in configure.in can use the VERSION file. See Section

2.11.6, “MySQL Configuration and Third-Party Tools.”

Functionality added or changed:

* Support for the IBMDB2I storage engine has been removed.

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

* A –bind-address option has been added to a number of MySQL

client programs: mysql, mysqldump, mysqladmin, mysqlbinlog,

mysqlcheck, mysqlimport, and mysqlshow. This is for use on a

computer having multiple network interfaces, and enables you

to choose which interface is used to connect to the MySQL

server.

Bugs fixed:

* Performance: InnoDB Storage Engine: Improved concurrency when

several ANALYZE TABLE or SHOW TABLE STATUS statements are run

simultaneously for InnoDB tables.

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

* Incompatible Change: Previously, tables in the

performance_schema database had uppercase names. This was

incompatible with the lower_case_table_names system variable,

and caused issues when the variable value was changed after

installing or upgrading.

Now performance_schema table names are lowercase, so they

appear in uniform lettercase regardless of the

lower_case_table_names setting. References to these tables in

SQL statements should be given in lowercase. This is an

incompatible change, but provides compatible behavior across

different values of lower_case_table_names.

If you upgrade to MySQL 5.5.8 from an earlier version of MySQL

5.5, be sure to run mysql_upgrade (and restart the server) to

change the names of existing performance_schema tables from

uppercase to lowercase.

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

* Incompatible Change: The following changes were made to the

performance_schema.threads table for conformance with the

implementation in MySQL 5.6:

+ ID column: Renamed to PROCESSLIST_ID, removed NOT NULL

from definition.

+ NAME column: Changed from VARCHAR(64) to VARCHAR(128).

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

* Incompatible Change: Deadlock occurred when a connection that

had some table open through a HANDLER statement tried to

update data through a DML statement while another connection

tried to execute FLUSH TABLES WITH READ LOCK concurrently.

Starvation of FLUSH TABLES WITH READ LOCK statements occurred

when there was a constant load of concurrent DML statements in

two or more connections.

These problems resulted from the global read lock

implementation, which was reimplemented with the following

consequences:

+ To solve deadlock in event-handling code that was exposed

by this patch, the LOCK_event_metadata mutex was replaced

with metadata locks on events. As a result, DDL operations

on events are now prohibited under LOCK TABLES. This is

an incompatible change.

+ The global read lock (FLUSH TABLES WITH READ LOCK) no

longer blocks DML and DDL on temporary tables. Before

this patch, server behavior was not consistent in this

respect: In some cases, DML/DDL statements on temporary

tables were blocked; in others, they were not. Since the

main use cases for FLUSH TABLES WITH READ LOCK are

various forms of backups and temporary tables are not

preserved during backups, the server now consistently

allows DML/DDL on temporary tables under the global read

lock.

+ Thread state names are now either Waiting for global read

lock or Waiting for commit lock, depending on which stage

FLUSH TABLES WITH READ LOCK is in.

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

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

* InnoDB Storage Engine: Values could be truncated in certain

INFORMATION_SCHEMA columns, such as

REFERENTIAL_CONSTRAINTS.REFERENCED_TABLE_NAME and

KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME.

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

* InnoDB Storage Engine: 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#57799: http://bugs.mysql.com/bug.php?id=57799)

* InnoDB Storage Engine: The server could stop with an assertion

error on Windows Vista and Windows 7 systems.

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

* InnoDB Storage Engine: A followup fix to

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

TABLE could still cause a crash (assertion error) in the

debug version of the server.

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

* InnoDB Storage Engine: The InnoDB system tablespace could grow

continually for a server under heavy load.

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

* InnoDB Storage Engine: Heavy concurrent updates of a BLOB

column in an InnoDB table could cause a hang.

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

* InnoDB Storage Engine: The innodb_stats_on_metadata option

could prevent the ANALYZE TABLE statement from running.

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

* InnoDB Storage Engine: A query for an InnoDB table could

return the wrong value if a column value was changed to a

different case, and the column had a case-insensitive index.

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

* InnoDB Storage Engine: An existing InnoDB could be switched to

ROW_FORMAT=COMPRESSED implicitly by a KEY_BLOCK_SIZE clause in

an ALTER TABLE statement. Now, the row format is only switched

to compressed if there is an explicit ROW_FORMAT=COMPRESSED

clause. on the ALTER TABLE statement.

Any valid, non-default ROW_FORMAT parameter takes precedence

over KEY_BLOCK_SIZE when both are specified. KEY_BLOCK_SIZE

only enables ROW_FORMAT=COMPRESSED if ROW_FORMAT is not

specified on either the CREATE TABLE or ALTER TABLE statement,

or is specified as DEFAULT. In case of a conflict between

KEY_BLOCK_SIZE and ROW_FORMAT clauses, the KEY_BLOCK_SIZE is

ignored if innodb_strict_mode is off, and the statement causes

an error if innodb_strict_mode is on.

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

* InnoDB Storage Engine: The clause KEY_BLOCK_SIZE=0 is now

allowed on CREATE TABLE and ALTER TABLE statements for InnoDB

tables, regardless of the setting of innodb_strict_mode. The

zero value has the effect of resetting the KEY_BLOCK_SIZE

table parameter to its default value, depending on the

ROW_FORMAT parameter, as if it had not been specified. That

default is 8 if ROW_FORMAT=COMPRESSED. Otherwise,

KEY_BLOCK_SIZE is not used or stored with the table

parameters.

As a consequence of this fix, ROW_FORMAT=FIXED is not allowed

when the innodb_strict_mode is enabled.

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

* InnoDB Storage Engine: A large number of foreign key

declarations could cause the output of the SHOW CREATE

STATEMENT statement to be truncated.

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

* InnoDB Storage Engine: A compilation problem affected the

InnoDB source code on NetBSD/sparc64.

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

* InnoDB Storage Engine: Clarified the message when a CREATE

TABLE statement fails because a foreign key constraint does

not have the required indexes.

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

* Partitioning: “Fast” ALTER TABLE operations (that do not

involve a table copy) on a partitioned table could leave the

table in an unusable state.

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

* Partitioning: An INSERT … ON DUPLICATE KEY UPDATE column = 0

statement on an AUTO_INCREMENT column caused the debug server

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

* Replication: Concurrent statements using a stored function and

a DROP DATABASE statement that caused the same stored function

to be dropped could cause statement-based replication to fail.

This problem is resolved by making sure that DROP DATABASE

takes an exclusive metadata lock on all stored functions and

stored procedures that it causes to be dropped.

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

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

* Replication: When STOP SLAVE is issued, the slave SQL thread

rolls back the current transaction and stops immediately if

the transaction updates only tables which use transactional

storage engines are updated. Previously, this occurred even

when the transaction contained CREATE TEMPORARY TABLE

statements, DROP TEMPORARY TABLE statements, or both, although

these statements cannot be rolled back. Because temporary

tables persist for the lifetime of a user session (in the

case, the replication user), they remain until the slave is

stopped or reset. When the transaction is restarted following

a subsequent START SLAVE statement, the SQL thread aborts with

an error that a temporary table to be created (or dropped)

already exists (or does not exist, in the latter case).

Following this fix, if an ongoing transaction contains CREATE

TEMPORARY TABLE statements, DROP TEMPORARY TABLE statements,

or both, the SQL thread now waits until the transaction ends,

then stops.

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

* Replication: If there exist both a temporary table and a

non-temporary table having the same, updates normally apply

only to the temporary table, with the exception of a CREATE

TABLE … SELECT statement that creates a non-temporary table

having the same name as an existing temporary table. When such

a statement was replicated using the MIXED logging format, and

the statement was unsafe for row-based logging, updates were

misapplied to the temporary table.

Updates were also applied wrongly when a temporary table that

used a transactional storage engine was dropped inside a

transaction, followed by updates within the same transaction

to a non-temporary table having the same name.

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

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

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

* Replication: When making changes to relay log settings using

CHANGE MASTER TO, the I/O cache was not cleared. This could

result in replication failure when the slave attempted to read

stale data from the cache and then stopped with an assertion.

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

* Replication: Replication of SET and ENUM columns represented

using more than 1 byte (that is, SET columns with more than 8

members and ENUM columns with more than 256 constants) between

platforms using different endianness failed when using the

row-based format. This was because columns of these types are

represented internally using integers, but the internal

functions used by MySQL to handle them treated them as

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

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

* Replication: Trying to read from a binary log containing a log

event of an invalid type caused the slave to crash.

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

* Replication: When replicating the mysql.tables_priv table, the

Grantor column was not replicated, and was thus left empty on

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

* Setting the read_only system variable at server startup did

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

* mysql_upgrade failed after an upgrade from MySQL 5.1.

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

* When configuring the build with -DBUILD_CONFIG=mysql_release

and building with Visual Studio Express, the build failed if

signtool.exe was not present.

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

* When configuring the build with -DBUILD_CONFIG=mysql_release

on Linux, libaio is required, but the error message if it was

missing was uninformative.

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

* Use of NAME_CONST() in a HAVING clause caused a server crash.

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

* BETWEEN did not use indexes for DATE or DATETIME columns.

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

* Memory was allocated in fn_expand() for storing path names,

but not freed anywhere.

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

* In debug builds, inserting a FLOAT value into a CHAR(0) column

could crash the server.

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

* Failure to create a thread to handle a user connection could

result in a server crash.

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

* During configuration, ADD_VERSION_INFO in

cmake/mysql_version.cmake failed if LINK_FLAGS was modified.

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

* Performance Schema did not account for I/O for the binary log

file (no I/O was counted).

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

* Several compilation problems were fixed.

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

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

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

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

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

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

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

* After creating a table with two foreign key constraints, the

INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS table displayed

only one of them.

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

* Incorrect error handling raised an assertion if character set

conversion wrapped an item that failed.

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

* In debug builds, a missing DBUG_RETURN macro in sql/client.c

caused mysql to be unable to connect to the server.

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

* Clients using a client library older than MySQL 5.5.7 suffered

loss of connection after executing mysql_change_user() while

connected to a 5.5.7 server.

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

* The MySQL-shared RPM package failed to provide the lowercase

virtual identifier ‘mysql-shared’ in the RPM ‘Provides’ tags

(usually used for backward compatibility).

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

* For an upgrade to MySQL 5.5.7 from a previous release, the

server exited if the mysql.proxies_priv table did not exist,

making upgrades inconvenient. Now the server treats a missing

proxies_priv table as equivalent to an empty table. However,

after starting the server, you should still run mysql_upgrade

to create the table.

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

* SHOW PROCESSLIST displayed non-ASCII characters improperly.

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

* Passing a string that was not null-terminated to UpdateXML()

or ExtractValue() caused the server to fail with an assertion.

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

* SET GLOBAL debug could cause a crash on Solaris if the server

failed to open the trace file.

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

* In debug builds, an assertion could be raised during

conversion of strings to floating-point values.

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

* A user with no privileges on a stored routine or the

mysql.proc table could discover the routine’s existence.

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

* Queries executed using the Index Merge access method and a

temporary file could return incorrect results.

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

* The server could crash as a result of accessing freed memory

when populating INFORMATION_SCHEMA.VIEWS if a view could not

be opened properly.

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

* Valgrind warnings about overlapping memory when

double-assigning the same variable were corrected.

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

* If a STOP SLAVE statement was issued while the slave SQL

thread was executing a statement that invoked the SLEEP()

function, both statements hung.

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

* OPTIMIZE TABLE for InnoDB tables could raise an assertion.

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

* Warnings raised by a trigger were not cleared upon successful

completion. Now warnings are cleared if the trigger completes

successfully, per the SQL standard.

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

* For CMake builds, some parts of the source were unnecessarily

compiled twice if the embedded server was built.

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

* Boolean command options caused an error if given with an

option value and the loose- option prefix.

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

* An error in a stored procedure could leave the session in a

different default database.

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

* The CMake “wrapper” for configure (configure.pl) did not

handle the –with-comment option properly.

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

* Grouping by a TIME_TO_SEC() function result could cause a

server crash or incorrect results. Grouping by a function

returning a BLOB could cause an unexpected “Duplicate entry”

error and incorrect result.

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

* The find_files() function used by SHOW statements performed

redundant and unnecessary memory allocation.

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

* The Windows sample option files contained values more

appropriate for Linux.

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

* A failed RENAME TABLE operation could prevent a FLUSH TABLES

WITH READ LOCK from completing.

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

* Error messages for several internal conditions that should not

occur were changed to instruct the user to file a bug if they

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

* On file systems with case insensitive file names, and

lower_case_table_names=2, the server could crash due to a

table definition cache inconsistency.

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

* Handling of host name lettercase in GRANT statements was

inconsistent.

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

* SET NAMES utf8 COLLATE utf8_sinhala_ci did not work.

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

* The utf16_bin collation uses code-point order, not

byte-by-byte order, as described at Section 9.1.14.1, “Unicode

Character Sets.” (The order was byte-by-byte in MySQL 5.5.7.)

MySQL Community Server 5.1.51

Phil Smith — Tue, 28 Sep 2010 09:49:23 +0000

MySQL Community Server 5.1.51, has been released. MySQL 5.1.51 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.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)

MySQL Community Server 5.1.49

Phil Smith — Fri, 23 Jul 2010 21:17:05 +0000

MySQL Community Server 5.1.49, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.49 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.49 on new servers or upgrading to MySQL 5.1.49 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html

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-49.html

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

C.1.2. Changes in MySQL 5.1.49 (09 July 2010)

    InnoDB Notes:

      * InnoDB Plugin has been upgraded to version 1.0.10. This
        version is considered of General Availability (GA) quality.
        InnoDB Plugin Change History
        (http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-changes.
        html), 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.

    Bugs fixed:

      * Replication: When using unique keys on NULL columns in
        row-based replication, the slave sometimes chose the wrong row
        when performing an update. This happened because a table
        having a unique key on such a column could have multiple rows
        containing NULL for the column used by the unique key, and the
        slave merely picked the first row containing NULL in that
        column. (Bug#53893: http://bugs.mysql.com/bug.php?id=53893)

      * Replication: FLUSH LOGS could in some circumstances crash the
        server. This occurred because the I/O thread could
        concurrently access the relay log I/O cache while another
        thread was performing the FLUSH LOGS, which closes and reopens
        the relay log and, while doing so, initializes (or
        re-initializes) its I/O cache. This could cause problems if
        some other thread (in this case, the I/O thread) is accessing
        it at the same time.
        Now the thread performing the FLUSH LOGS takes a lock on the
        relay log before actually flushing it.
        (Bug#53657: http://bugs.mysql.com/bug.php?id=53657)
        See also Bug#50364: http://bugs.mysql.com/bug.php?id=50364.

      * Replication: Two related issues involving temporary tables and
        transactions were introduced by a fix made in MySQL 5.1.37:

          1. When a temporary table was created or dropped within a
             transaction, any failed statement that following the
             CREATE TEMPORARY TABLE or DROP TEMPORARY TABLE statement
             triggered a rollback, which caused the slave diverge from
             the master.

          2. When a CREATE TEMPORARY TABLE ... SELECT * FROM ...
             statement was executed within a transaction in which only
             tables using transactional storage engines were used and
             the transaction was rolled back at the end, the
             changes---including the creation of the temporary
             table---were not written to the binary log.
        The current fix restores the correct behavior in both of these
        cases. (Bug#53560: http://bugs.mysql.com/bug.php?id=53560)
        This regression was introduced by
        Bug#43929: http://bugs.mysql.com/bug.php?id=43929.

      * Replication: When CURRENT_USER() or CURRENT_USER was used to
        supply the name and host of the affected user or of the
        definer in any of the statements DROP USER, RENAME USER,
        GRANT, REVOKE, and ALTER EVENT, the reference to
        CURRENT_USER() or CURRENT_USER was not expanded when written
        to the binary log. This resulted in CURRENT_USER() or
        CURRENT_USER being expanded to the user and host of the slave
        SQL thread on the slave, thus breaking replication. Now
        CURRENT_USER() and CURRENT_USER are expanded prior to being
        written to the binary log in such cases, so that the correct
        user and host are referenced on both the master and the slave.
        (Bug#48321: http://bugs.mysql.com/bug.php?id=48321)

      * An ALTER TABLE statement could convert an InnoDB compressed
        table (with row_format=compressed) back to an uncompressed
        table (with row_format=compact).
        (Bug#54679: http://bugs.mysql.com/bug.php?id=54679)

      * A signal-handler redefinition for SIGUSR1 was removed. The
        redefinition could cause the server to encounter a kernel
        deadlock on Solaris when there are many active threads. Other
        POSIX platforms might also be affected.
        (Bug#54667: http://bugs.mysql.com/bug.php?id=54667)

      * InnoDB could issue an incorrect message on startup, if tables
        were created under the setting innodb_file_per_table=ON and
        the server was restarted under the setting
        innodb_file_per_table=OFF. The message was of the form InnoDB:
        Warning: allocated tablespace n, old maximum was 0.
        (Bug#54658: http://bugs.mysql.com/bug.php?id=54658)

      * The make_binary_distribution target to make could fail on some
        platforms because the lines generated were too long for the
        shell. (Bug#54590: http://bugs.mysql.com/bug.php?id=54590)

      * The server failed to disregard sort order for some zero-length
        tuples, leading to an assertion failure.
        (Bug#54459: http://bugs.mysql.com/bug.php?id=54459)

      * The default value of myisam_max_extra_sort_file_size
        (http://dev.mysql.com/doc/refman/5.0/en/server-system-variable
        s.html#sysvar_myisam_max_extra_sort_file_size) could be higher
        than the maximum accepted value, leading to warnings upon the
        server start.
        (Bug#54457: http://bugs.mysql.com/bug.php?id=54457)

      * If a session tried to drop a database containing a table
        opened with HANDLER in another session, any DATABASE statement
        (CREATE, DROP, ALTER) executed by that session produced a
        deadlock. (Bug#54360: http://bugs.mysql.com/bug.php?id=54360)

      * Fast index creation could fail, leaving the new secondary
        index corrupted.
        (Bug#54330: http://bugs.mysql.com/bug.php?id=54330)

      * 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)

      * Builds of the embedded mysqld would fail due to a missing
        element of the struct NET.
        (Bug#53908: http://bugs.mysql.com/bug.php?id=53908,
        Bug#53912: http://bugs.mysql.com/bug.php?id=53912)

      * The definition of the MY_INIT macro in my_sys.h included an
        extraneous semicolon, which could cause compilation failure.
        (Bug#53906: http://bugs.mysql.com/bug.php?id=53906)

      * A client with automatic reconnection enabled saw the error
        message Lost connection to MySQL server during query if the
        connection was lost between the mysql_stmt_prepare() and
        mysql_stmt_execute() C API functions. However,
        mysql_stmt_errno() returned 0, not the corresponding error
        number 2013.
        (Bug#53899: http://bugs.mysql.com/bug.php?id=53899)

      * Queries that used MIN() or MAX() on indexed columns could be
        optimized incorrectly.
        (Bug#53859: http://bugs.mysql.com/bug.php?id=53859)

      * The Lock_time value in the slow query log was negative for
        stored routines.
        (Bug#53191: http://bugs.mysql.com/bug.php?id=53191)

      * The results of some ORDER BY ... DESC queries were sorted
        incorrectly.
        (Bug#51431: http://bugs.mysql.com/bug.php?id=51431)

      * Index Merge between three indexes could return incorrect
        results. (Bug#50389: http://bugs.mysql.com/bug.php?id=50389)

      * Performing large numbers of RENAME TABLE statements caused
        excessive memory use.
        (Bug#47991: http://bugs.mysql.com/bug.php?id=47991)

      * The server could crash with an out of memory error when trying
        to parse a query that was too long to fit in memory. Now the
        parser rejects such queries with an ER_OUT_OF_RESOURCES error.
        (Bug#42064: http://bugs.mysql.com/bug.php?id=42064)

      * Sort-index_merge for join tables other than the first table
        used excessive memory.
        (Bug#41660: http://bugs.mysql.com/bug.php?id=41660)

      * Valgrind warnings in the InnoDB compare_record() function were
        corrected. (Bug#38999: http://bugs.mysql.com/bug.php?id=38999)

      * mysqld could fail during execution when using SSL.
        (Bug#34236: http://bugs.mysql.com/bug.php?id=34236)

      * The behavior of the RPM upgrade installation has changed.
        During an upgrade installation using the RPM packages, if the
        MySQL server is running when the upgrade occurs, the server is
        stopped, the upgrade occurs, and server is restarted. If the
        server is not already running when the RPM upgrade occurs, the
        server is not started at the end of the upgrade. The boot
        scripts for MySQL are installed in the appropriate directories
        in /etc, so the MySQL server will be restarted automatically
        at the next machine reboot.
        (Bug#27072: http://bugs.mysql.com/bug.php?id=27072)

MySQL Community Server 5.1.48

Phil Smith — Fri, 18 Jun 2010 09:27:38 +0000

MySQL Community Server 5.1.48, a new version of the popular Open Source Database Management System, has been released.

MySQL 5.1.48 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.48 on new servers or upgrading to MySQL 5.1.48 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.48 Functionality added or changed:

* The Rows_examined value in slow query log rows now is nonzero for UPDATE and DELETE statements that modify rows. (Bug#49756: http://bugs.mysql.com/bug.php?id=49756)

Bugs fixed:

* Important Change: Replication: MyISAM transactions replicated to a transactional slave left the slave in an unstable condition. This was due to the fact that, when replicating from a nontransactional storage engine to a transactional engine with autocommit turned off, no BEGIN and COMMIT statements were written to the binary log; thus, on the slave, a never-ending transaction was started. The fix for this issue includes enforcing autocommit mode on the slave by replicating all autocommit=1 statements from the master. (Bug#29288: http://bugs.mysql.com/bug.php?id=29288)

* Partitioning: ALTER TABLE statements that cause table partitions to be renamed or dropped (such as ALTER TABLE … ADD PARTITION, ALTER TABLE … DROP PARTITION, and ALTER TABLE … REORGANIZE PARTITION) — when run concurrently with queries against the INFORMATION_SCHEMA.PARTITIONS table — could fail, cause the affected partitioned tables to become unusable, or both. This was due to the fact that the INFORMATION_SCHEMA database ignored the name lock imposed by the ALTER TABLE statement on the partitions affected. In particular, this led to problems with InnoDB tables, because InnoDB would accept the rename operation, but put it in a background queue, so that subsequent rename operations failed when InnoDB was unable to find the correct partition. Now, INFORMATION_SCHEMA honors name locks imposed by ongoing ALTER TABLE statements that cause partitions to be renamed or dropped. (Bug#50561: http://bugs.mysql.com/bug.php?id=50561) See also Bug#47343: http://bugs.mysql.com/bug.php?id=47343, Bug#45808: http://bugs.mysql.com/bug.php?id=45808.

* Partitioning: It was possible to execute a CREATE TEMPORARY TABLE tmp LIKE pt statement, where pt is a partitioned table, even though partitioned temporary tables are not permitted, which caused the server to crash. Now a check is performed to prevent such statements from being executed. (Bug#49477: http://bugs.mysql.com/bug.php?id=49477)

* Partitioning: When attempting to perform DDL on a partitioned table and the table’s .par file could not be found, the server returned the inaccurate error message Out of memory; restart server and try again (needed 2 bytes). Now in such cases, the server returns the error Failed to initialize partitions from .par file. (Bug#49161: http://bugs.mysql.com/bug.php?id=49161)

* Replication: In some cases, attempting to update a column with a value of an incompatible type resulted in a mismatch between master and slave because the column value was set to its implicit default value on the master (as expected), but the same column on the slave was set to NULL. (Bug#52868: http://bugs.mysql.com/bug.php?id=52868)

* Replication: When using a non-transactional table on the master with autocommit disabled, no COMMIT was recorded in the binary log following a statement affecting this table. If the slave’s copy of the table used a transactional storage engine, the result on the slave was as though a transaction had been started, but never completed. (Bug#49522: http://bugs.mysql.com/bug.php?id=49522) See also Bug#29288: http://bugs.mysql.com/bug.php?id=29288.

* Replication: Reading from a table that used a self-logging storage engine and updating a table that used a transactional engine (such as InnoDB) generated changes that were written to the binary log using statement format which could make slaves diverge. However, when using mixed logging format, such changes should be written to the binary log using row format. (This issue did not occur when reading from tables using a self-logging engine and updating MyISAM tables, as this was already handled by checking for combinations of non-transactional and transactional engines.) Now such statements are classified as unsafe, and in mixed mode, cause a switch to row-based logging. (Bug#49019: http://bugs.mysql.com/bug.php?id=49019)

* Valgrind warnings resulting from passing incomplete DATETIME values to the TIMESTAMP() function were corrected. (Bug#53942: http://bugs.mysql.com/bug.php?id=53942)

* Builds of the embedded mysqld would fail due to a missing element of the struct NET. (Bug#53908: http://bugs.mysql.com/bug.php?id=53908, Bug#53912: http://bugs.mysql.com/bug.php?id=53912)

* UPDATE on an InnoDB table modifying the same index that was used to satisfy the WHERE condition could trigger a debug assertion under some circumstances. (Bug#53830: http://bugs.mysql.com/bug.php?id=53830)

* For single-table DELETE statements that used quick select and index scan simultaneously caused a server crash or assertion failure. (Bug#53450: http://bugs.mysql.com/bug.php?id=53450)

* Incorrect results could be returned for LEFT JOIN of InnoDB tables with an impossible WHERE condition. (Bug#53334: http://bugs.mysql.com/bug.php?id=53334)

* Fixed a checksum error reported for compressed tables when the –innodb_checksums option is enabled. (Bug#53248: http://bugs.mysql.com/bug.php?id=53248)

* Corrected the handling of the setting innodb_change_buffering=default. (The appropriate default value is different between MySQL 5.1 and 5.5.) (Bug#53165: http://bugs.mysql.com/bug.php?id=53165)

* mysqldump and SELECT … INTO OUTFILE truncated long BLOB and TEXT values to 766 bytes. (Bug#53088: http://bugs.mysql.com/bug.php?id=53088)

* In the debug version of the server, the FreeState() function could in some circumstances be called twice, leading to an assertion failure. (Bug#52884: http://bugs.mysql.com/bug.php?id=52884)

* Aggregate functions could incorrectly return NULL in outer join queries. (Bug#52051: http://bugs.mysql.com/bug.php?id=52051)

* The Loose Index Scan optimization method assumed that it could depend on the partitioning engine to maintain interval endpoint information, as if it were a storage engine. (Bug#50939: http://bugs.mysql.com/bug.php?id=50939)

* Calculation of intervals for Event Scheduler events was not portable. (Bug#50087: http://bugs.mysql.com/bug.php?id=50087)

* Selecting from INFORMATION_SCHEMA.ROUTINES or INFORMATION_SCHEMA.PARAMETERS (http://dev.mysql.com/doc/refman/5.5/en/parameters-table.html) resulted in a memory leak. (Bug#48729: http://bugs.mysql.com/bug.php?id=48729)

* When the transaction isolation level was REPEATABLE READ and binary logging used statement or mixed format, SELECT statements with subqueries referencing InnoDB tables unnecessarily acquired shared locks on rows in these tables. (Bug#46947: http://bugs.mysql.com/bug.php?id=46947)

* Using an initial command with mysql_options(…, MYSQL_INIT_COMMAND, …) that generated multiple result sets (such as a stored procedure or a multi-statement command) left the connection unusable. (Bug#42373: http://bugs.mysql.com/bug.php?id=42373)

* If a crash occurs while creating an index using the InnoDB “Fast Index Creation” mechanism, the partially created index is dropped during the crash recovery processing when the database is restarted.

MySQL Community Server 5.1.45

Phil Smith — Sat, 20 Mar 2010 18:39:55 +0000

MySQL Community Server 5.1.45, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.45 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.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

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)