Skip navigation links

Additional languages
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.3 Changes in release 3.23.x :: B.3.12 Changes in release 3.23.48 (07 February 2002)
B.3.13 Changes in release 3.23.47 (27 December 2001) »
Section Navigation      [Toggle]

B.3.12. Changes in release 3.23.48 (07 February 2002)

End of Product Lifecycle. Active development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Added --xml option to mysqldump for producing XML output.

  • Changed to use autoconf 2.52 (from autoconf 2.13)

  • Fixed bug in complicated join with const tables.

  • Added internal safety checks for InnoDB.

  • Some InnoDB variables were always shown in SHOW VARIABLES as OFF on high-byte-first systems (like SPARC).

  • Fixed problem with one thread using an InnoDB table and another thread doing an ALTER TABLE on the same table. Before that, mysqld could crash with an assertion failure in row0row.c, line 474.

  • Tuned the InnoDB SQL optimizer to favor index searches more often over table scans.

  • Fixed a performance problem with InnoDB tables when several large SELECT queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT queries now also generally run faster on all platforms.

  • If MySQL binary logging is used, InnoDB now prints after crash recovery the latest MySQL binary log name and the offset InnoDB was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication.

  • Added better error messages to help in installation problems of InnoDB tables.

  • It is now possible to recover MySQL temporary tables that have become orphaned inside the InnoDB tablespace.

  • InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns.

  • Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld crash. Especially at risk was mysqldump, because it frequently calls SHOW CREATE TABLE.

  • If inserts to several tables containing an AUTO_INCREMENT column were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c.

  • In 3.23.47 we allowed several NULL values in a UNIQUE secondary index for an InnoDB table. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation.

  • SHOW GRANTS now shows REFERENCES instead of REFERENCE.