When creating a new partition, a bogus memory allocation problem was
reported.

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into lmy004.:/work/mysql-5.1-bug16410

into lmy004.:/work/mysql-5.1-bug16410

into serg.mylan:/usr/home/serg/Abk/mysql-5.1

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.1-clean

KEY event. Partitioning wrongly claimed to be able to handle HA_DUPP_POS
when it was supported by the underlying storage engine, which resulted
in a crash when handling REPLACE statements.

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

into lmy004.:/work/mysql-5.1-bug17289

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into lmy004.:/work/mysql-5.1-bug16410

WL#1034 (Internal CRON)
(post-post-review updates)

into  mysql.com:/home/jimw/my/mysql-4.1-clean

into serg.mylan:/usr/home/serg/Abk/mysql-5.1

into  zim.tangent.org:/home/brian/mysql/archive-5.1

into lmy004.:/work/mysql-5.1-bug17289

 - Change 94 to 95 according to Pem's instructions in bug report.

into serg.mylan:/usr/home/serg/Abk/mysql-5.1

 - Init sql_state in mysql_stmt_init

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-work

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

  In presense of subpartitioning use get_part_partition_id() to calculate part_id

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-work

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

  use part_info->no_subparts to calculate partition range in case of subpartitions

This patch adds a new field to the meta file for tracking flushes (this is being kept to later do stats and determine how often the compression buffer is being foiled). This should keep things all nice an compatible between versions.
Also added a flush table test as well. Found one possible bug in OPTIMIZE TABLE which has never been reported, but I think it would be possible on a file system that ran out of disk.