Add patch to fix the failing main.variables mysql-test. It started failing
after the variable innodb_use_sys_malloc was added because it matches
'%alloc%' and the test is badly written and expects that no new variables
like that will ever be added.
@@GLOBAL.innodb_file_per_table can be 0 or 1, while
SELECT VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES
WHERE VARIABLE_NAME='innodb_file_per_table'
can be 'OFF' or 'ON'. For some reason, MySQL evaluates
(0 = 'OFF') to 1 and (1 = 'ON') to 0. Thus, the test would
fail if innodb_file_per_table is set.
type_bit_innodb.diff: Ignore the reported duplicate value. The reported
value depends on the internal workings of the merge sort in
fast index creation. In the built-in InnoDB of MySQL 5.1, the records
are copied to a new temporary table in the order they were selected from
the original table.
information_schema.diff: Account for the INFORMATION_SCHEMA tables that
were added in the InnoDB plugin.
innodb_file_per_table.diff: In the InnoDB plugin, innodb_file_per_table
is a settable global variable.
Change the patch to fix the failing mysql-test index_merge_innodb.
The previous variant is inappropriate because myisam results are different
(2 instead of 4) and then the index_merge_myisam test fails.
Add a patch to fix the failing mysql-test index_merge_innodb. The test
started failing after an optimization, made in r2625, which results in
a different number of rows being returned by EXPLAIN.
