Fonctionnalité ajoutée ou modifiée :
Bogues corrigés :
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
.err log. The workaround is to make
enough to hold all memory allocation. Use
INNODB STATUS to determine that there is plenty of
free space available in the additional mem pool, and the
total allocated memory stays rather constant.
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
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.