Software Update: MySQL 3.23.53

Stephan Oudmaijer announced that a new version of MySQL has been released. You can download the source code and binaries for the various operating systems here to download. The changelog of MySQL 3.23.53 reads as follows:

• Small fix in safe_mysqld for some shells.
• Fixed that SHOW STATUS doesn’t reset Delayed_insert_threads.
• Fixed core dump bug when using the BINARY cast on a NULL value.
• Fixed race condition when someone did a GRANT at the same time a new user logged in or did a USE DATABASE.
• Fixed bug in ALTER TABLE and RENAME TABLE when running with -O lower_case_table_names=1 (typically on windows) when giving the table name in uppercase.
• Fixed that -O lower_case_table_names=1 also converts database names to lower case.
• Fixed unlikely core dump with SELECT … ORDER BY … LIMIT.
• Changed AND/OR to report that they can return NULL. This fixes a bug in GROUP BY on AND/OR expressions that return NULL.
• Fixed a bug that OPTIMIZE of locked and modified MyISAM table, reported table corruption.
• Fixed a BDB-related ALTER TABLE bug with dropping a column and shutting down immediately thereafter.
• Fixed problem with configure … –localstatedir=….
• Fixed problem with UNSIGNED BIGINT on AIX (again).
• Fixed bug in pthread_mutex_trylock() on HPUX 11.0.
• Multithreaded stress tests for InnoDB.

[break] The InnoDB table handler in version 3.23.53 has the following changes undergo: [/break]

• We again use unbuffered disk i/o to data files in Windows. Win XP and Win 2000 read performance seems to be very poor with normal i/o.
• Tuned range estimator so that index range scans are preferred over full index scans.
• Allow dropping and creating a table even if innodb_force_recovery is set. One can use this to drop a table which would cause a crash in rollback or purge, or if a failed table import causes a runaway rollback in recovery.
• Fixed a bug present in 3.23.52, 4.0.3, 4.0.4: InnoDB startup could take very long or even crash on some Win 95/98/ME computers.
• Fixed a bug: fast shutdown (which is the default) sometimes was slowed down by purge and insert buffer merge.
• Fixed a bug: doing a big SELECT from a table where no rows were visible in a consistent read could cause a very long (> 600 seconds) semaphore wait in btr0cur.c line 310.
• Fixed a bug: the AUTO-INC lock was held to the end of the transaction if it was granted after a lock wait. This could cause unnecessary deadlocks.
• Fixed a bug: if you created a temporary table inside LOCK TABLES, and used that temporary table, that caused an assertion failure in ha_innobase.cc.
• Fixed a bug: if SHOW INNODB STATUS, innodb_monitor, or innodb_lock_monitor had to print several hundred transactions in one report, and the output became truncated, InnoDB would hang, printing to the error log many waits for a mutex created at srv0srv.c, line 1621.
• Fixed a bug: SHOW INNODB STATUS on Unix always reported average file read size as 0 bytes.