Software Update: MySQL 3.23.49

A week after the release of MySQL 3.23.48, MySQL AB already has a new version released† The binary release of 3.23.48 used a new glibc library that was found to have problems under high load and Red Had Linux 7.2. This issue no longer exists in the 3.23.49 binary. There are also a few bug fixes in this version:

Changes in release 3.23.49:

• Don’t give warning for statement that is only a comment; This is needed for mysqldump –disable-keys to work.
• Fixed unlikely caching bug when doing a join without keys. In this case the last used field for a table always returned NULL.
• Added options to make LOAD DATA LOCAL INFILE more secure.
• MySQL binary release 3.23.48 for Linux contained a new glibc library, which has serious problems under high load and RedHat 7.2. The 3.23.49 binary release doesn’t have this problem.

InnoDB bug fixes

• February 15, 2002: If you run mysqld-max-nt as a service on Windows NT/2000, the service shutdown does not always wait long enough for the InnoDB shutdown to finish. The safest way is to run mysqld-max-nt from a MS-DOS prompt, and use the command ‘mysqladmin shutdown’ to shut down it. Partially fixed at 3.23.48.
• February 14, 2002: If you call DROP DATABASE for a database on which there simultaneously are running queries, the MySQL server may crash or hang. Crashes fixed in 3.23.49, but a full fix has to wait some changes in the MySQL layer of code.
• February 13, 2002: On Windows one had to put the database name in lower case for DROP DATABASE to work. Fixed in 3.23.49: case no longer matters on Windows. On Unix the database name remains case-sensitive.
• February 10, 2002: If one defines a non-latin1 character set as the default character set, then definition of foreign key constraints may fail in an assertion failure in dict0crea.c, reporting an internal error 17. Fixed in 3.23.49 and 4.0 .2. A source code patch can be found here.