Skip navigation links
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.3 Changes in Release 3.23.x :: B.3.19 Changes in Release 3.23.41 (11 August 2001)
B.3.20 Changes in Release 3.23.40 (18 July 2001) »
Section Navigation      [Toggle]

B.3.19. Changes in Release 3.23.41 (11 August 2001)

End of Product Lifecycle. Active development and support for MySQL Database Server versions 3.23, 4.0, and 4.1 has ended. For details, see http://www.mysql.com/about/legal/lifecycle/#calendar. Please consider upgrading to a recent version. Further updates to the content of this manual will be minimal. All formats of this manual will continue to be available until 31 Dec 2010.

  • Added --sql-mode=value[,value[,value]] option to mysqld. See Section 5.1.2, “Server Command Options”.

  • Fixed possible problem with shutdown on Solaris where the .pid file wasn't deleted.

  • InnoDB now supports < 4GB rows. The former limit was 8000 bytes.

  • The doublewrite file flush method is used in InnoDB. It reduces the need for Unix fsync() calls to a fraction and improves performance on most Unix flavors.

  • You can now use the InnoDB Monitor to print a lot of InnoDB state information, including locks, to the standard output. This is useful in performance tuning.

  • Several bugs which could cause hangs in InnoDB have been fixed.

  • Split record_buffer to record_buffer and record_rnd_buffer. To make things compatible to previous MySQL versions, if record_rnd_buffer is not set, then it takes the value of record_buffer.

  • Fixed optimizing bug in ORDER BY where some ORDER BY parts where wrongly removed.

  • Fixed overflow bug with ALTER TABLE and MERGE tables.

  • Added prototypes for my_thread_init() and my_thread_end() to mysql_com.h

  • Added --safe-user-create option to mysqld.

  • Fixed bug in SELECT DISTINCT ... HAVING that caused error message Can't find record in #...