CRITICAL BUG in 4.1.2 if you specify
innodb_file_per_table
in
my.cnf
on Unix. In crash recovery InnoDB
skips the crash recovery for all .ibd
files
and those tables become CORRUPT! The symptom is a message
Unable to lock ...ibd with lock 1, error: 9: fcntl: Bad
file descriptor
in the .err
log
in crash recovery.
Functionality added or changed:
Support multiple character sets. Note that tables created in
other collations than latin1_swedish_ci
cannot be accessed in MySQL/InnoDB 4.0.
Automatically create a suitable index on a FOREIGN
KEY
, if the user does not create one. Removes most
of the cases of Error 1005 (errno 150)
in
table creation.
Do not assert in log0log.c
, line 856 if
ib_logfiles
are too small for
innodb_thread_concurrency
.
Instead, print instructions how to adjust
my.cnf
and call
exit(1)
.
If MySQL tries to SELECT
from
an InnoDB table without setting any table locks, print a
descriptive error message and assert; some subquery bugs were
of this type.
Allow a key part length in InnoDB to be up to 3,500 bytes; this is needed so that you can create an index on a column with 255 UTF-8 characters.
All new features from InnoDB-4.0.17, InnoDB-4.0.18, InnoDB-4.0.19 and InnoDB-4.0.20.
Bugs fixed:
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 the one following in the
.err
log.
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
Improved portability to 64-bit platforms, especially Win64.
Fixed an assertion failure when a purge of a table was not
possible because of missing .ibd
file.
Fixed a bug: do not retrieve all columns in a table if we only
need the 'ref' of the row (usually, the PRIMARY
KEY
) to calculate an ORDER BY
.
(Bug#1942)
On Unix-like systems, obtain an exclusive advisory lock on InnoDB files, to prevent corruption when multiple instances of MySQL are running on the same set of data files. The Windows version of InnoDB currently takes a mandatory lock on the files. (Bug#3608)
Added a missing space to the output format of
SHOW INNODB STATUS
; reported by
Jocelyn Fournier.
All bugfixes from InnoDB-4.0.17, InnoDB-4.0.18, InnoDB-4.0.19 and InnoDB-4.0.20.
User Comments
Add your own comment.