Bug#11853126 RE-ENABLE CONCURRENT READS WHILE CREATING

SECONDARY INDEX IN INNODB

This is a follow-up patch.

This patch moves part of the new test coverage to a test
file that is only run on debug builds since it used debug-
only features and therefore broke the test case on
release builds.

mysql-test/r/innodb_mysql_lock.result

@@ -153,7 +153,6 @@ DROP VIEW v1;
 #              KEY NO 0 FOR TABLE IN ERROR LOG 
 #
 DROP TABLE IF EXISTS t1;
-# Test 1: Secondary index
 # Connection default
 CREATE TABLE t1 (id INT PRIMARY KEY, value INT) ENGINE = InnoDB;
 INSERT INTO t1 VALUES (1, 12345);
@@ -173,20 +172,3 @@ id	value
 1	12345
 COMMIT;
 DROP TABLE t1;
-# Test 2: Primary index
-CREATE TABLE t1(a INT NOT NULL, b INT NOT NULL) engine=innodb;
-INSERT INTO t1 VALUES (1, 12345), (2, 23456);
-# Connection con1
-SET SESSION debug= "+d,alter_table_rollback_new_index";
-ALTER TABLE t1 ADD PRIMARY KEY(a);
-ERROR HY000: Unknown error
-SELECT * FROM t1;
-a	b
-1	12345
-2	23456
-# Connection default
-SELECT * FROM t1;
-a	b
-1	12345
-2	23456
-DROP TABLE t1;