Fonctionnalité ajoutée ou modifiée :
Important: Made internal
TIMESTAMP values in
InnoDB in 4.1 to be the same as in 4.0.
This difference resulted in incorrect datetime values in
TIMESTAMP columns in
InnoDB tables after an upgrade from 4.0
to 4.1. (Bug #4492) Warning: extra
steps during upgrade required! This means that if
you are upgrading from 4.1.x, where x <= 3, to 4.1.4 you
mysqldump for saving and then
InnoDB tables with
TIMESTAMP columns. No conversion is
needed if you upgrade from 3.23 or 4.0 to 4.1.4 or later.
Added a new startup option
InnoDB not to use next-key
locking in searches and index scans.
innodb_status_file system variable
to mysqld to control whether output from
SHOW INNODB STATUS is written to a
file in the data directory. By default, the file is not
created. To create it, start mysqld with
Changes for NetWare to exit InnoDB gracefully on NetWare even in a case of an assertion failure, instead of intentionally crashing the mysqld server process.
Bogues corrigés :
Fixed a bug in
ON DELETE CASCADE and
ON UPDATE CASCADE foreign key
constraints: long chains of cascaded operations would cause
a stack overflow and crash the server. Cascaded operations
are now limited to 15 levels. (Bug #4446)
Increment the InnoDB watchdog timeout during
TABLE. (Bug #2694)
If you configure
innodb_additional_mem_pool_size so small
that InnoDB memory allocation spills over from it, then
every 4 billionth spill may cause memory corruption. A
symptom is a printout like below in the
InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the InnoDB: previous allocated area! InnoDB: Apparent memory corruption: mem dump len 500; hex
Fixed a glitch introduced in 4.0.18 and 4.1.2: in
SHOW TABLE STATUS InnoDB systematically
overestimated the row count by 1 if the table fit on a
single 16 kB data page.
InnoDB created temporary files with the C library function
tmpfile(). On Windows, the files would be
created in the root directory of the current file system. To
correct this behavior, the invocations of
tmpfile() were replaced with code that
uses the function
the MySQL portability layer. (Bug #3998)
RENAMEd a table, InnoDB forgot to
load the foreign key constraints that reference the new
table name, and forgot to check that they are compatible
with the table.
If there was little file I/O in InnoDB, but the insert buffer was used, it could happen that 'Pending normal aio reads' was bigger than 0, but the I/O handler thread did not get waken up in 600 seconds. This resulted in a hang, and an intentional crashing of mysqld.
This is a translation of the MySQL Reference Manual that can be found at dev.mysql.com. The original Reference Manual is in English, and this translation is not necessarily as up to date as the English version.