MySQL Community Server 5.1.51
# 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...
View ArticleMySQL Community Server 5.1.50
# 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...
View ArticleMySQL Community Server 5.1.49
# 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...
View ArticleMySQL Community Server 5.1.48
# 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...
View ArticleMySQL Community Server 5.1.47
# Bugs fixed:* Important Change: Replication: When invoked, CHANGE MASTER TO and SET GLOBAL sql_slave_skip_counter now cause information to be written to the error log about the slave's state prior to...
View ArticleMySQL Community Server 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 may contain information in...
View ArticleMySQL Community Server 5.1.45
# 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...
View ArticleMySQL Community Server 5.1.44
# 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...
View ArticleMySQL Community Server 5.1.43
# Bugs fixed:* Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us...
View ArticleMySQL Community Server 5.1.42
# 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...
View ArticleMySQL Community Server 5.1.41
# Functionality added or changed:* The InnoDB buffer pool is divided into two sublists: A new sublist containing blocks that are heavily used by queries, and an old sublist containing less-used blocks...
View ArticleMySQL Community Server 5.1.40
Bugs fixed:* Incompatible Change: In binary installations of MySQL, the supplied binary-configure script would start and configure MySQL, even when request help on the command with the --help...
View ArticleMySQL Community Server 5.1.39
Bugs fixed:* Partitioning: An INSERT ... SELECT statement on an empty partition of a partitioned table failed with ERROR 1030 (HY000): Got error 124 from storage engine. This issue also caused queries...
View ArticleMySQL Community Server 5.1.38
#Functionality added or changed: * The InnoDB Plugin is included in MySQL releases, in addition to the built-in version of InnoDB that has been included in previous releases. This version of the...
View ArticleMySQL Community Server 5.1.37
* Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the output of SHOW SLAVE STATUS....
View ArticleMySQL Community Server 5.1.36
Functionality added or changed: * Important Change: Replication: Previously, incident log events were represented as comments in the output from mysqlbinlog, making them effectively silent when...
View ArticleMySQL Community Server 5.1.35
* The .msi installer does not detect an existing root password on the initial configuration attempt. To work around this, install and configure MySQL as normal, but skip any changes to security....
View ArticleMySQL Community Server 5.1.34
* Replication: Important Note: Binary logging with --binlog_format=ROW failed when a change to be logged included more than 251 columns. This issue was not known to occur with mixed-format or...
View ArticleMySQL Community Server 5.1.33
Functionality added or changed: * mysql-test-run.pl now supports an --experimental=file_name option. It enables you to specify a file that contains a list of test cases that should be displayed with...
View ArticleMySQL Community Server 5.1.32
Functionality added or changed: * Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the...
View Article