Bug #26334149 - MYSQL CRASHES WHEN FULL TEXT INDEXES IBD FILES

ARE ORPHANED DUE TO RENAME TABLE

Post-push testcase innodb-alter fix.

Author: sachinagarwal1111

mysql-test/suite/innodb/r/innodb-alter.result

@@ -831,14 +831,14 @@ DROP TABLE t1;
 #
 CREATE DATABASE db1;
 USE db1;
-CREATE TABLE `notes` (
-`id` int(11) NOT NULL AUTO_INCREMENT,
-`body` text COLLATE utf8_unicode_ci,
-PRIMARY KEY (`id`)
+CREATE TABLE notes (
+id int(11) NOT NULL AUTO_INCREMENT,
+body text COLLATE utf8_unicode_ci,
+PRIMARY KEY (id)
 ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8
 COLLATE=utf8_unicode_ci
 ROW_FORMAT=COMPRESSED;
-ALTER TABLE notes ADD FULLTEXT INDEX `index_ft_body` (body(255));
+ALTER TABLE notes ADD FULLTEXT INDEX index_ft_body (body(255));
 Warnings:
 Warning	124	InnoDB rebuilding table to add column FTS_DOC_ID
 DROP INDEX index_ft_body ON notes;

mysql-test/suite/innodb/t/innodb-alter.test

@@ -473,7 +473,7 @@ CREATE DATABASE db1; USE db1;
 CREATE TABLE notes (
    id int(11) NOT NULL AUTO_INCREMENT,
    body text COLLATE utf8_unicode_ci,
-   PRIMARY KEY (`id`)
+   PRIMARY KEY (id)
    ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8
 COLLATE=utf8_unicode_ci
 ROW_FORMAT=COMPRESSED;