mariadb/mysql-test/r/partition_binlog_stmt.result

DROP TABLE IF EXISTS t1;
#
# Bug#51851: Server with SBR locks mutex twice on LOAD DATA into
#            partitioned MyISAM table
CREATE TABLE t1
(id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
name TINYBLOB NOT NULL,
modified TIMESTAMP DEFAULT '0000-00-00 00:00:00',
INDEX namelocs (name(255))) ENGINE = MyISAM
PARTITION BY HASH(id) PARTITIONS 2;
LOAD DATA LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/init_file.txt'
INTO TABLE t1 (name);
DROP TABLE t1;
Bug#51851: Server with SBR locks mutex twice on LOAD DATA into partitioned MyISAM table Problem was that both partitioning and myisam used the same table_share->mutex for different protections (auto inc and repair). Solved by adding a specific mutex for the partitioning auto_increment. Also adding destroying the ha_data structure in free_table_share (which is to be propagated into 5.5). This is a 5.1 ONLY patch, already fixed in 5.5+. 2010-10-01 13:39:04 +02:00			`DROP TABLE IF EXISTS t1;`
			`#`
			`# Bug#51851: Server with SBR locks mutex twice on LOAD DATA into`
			`# partitioned MyISAM table`
			`CREATE TABLE t1`
			`(id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,`
			`name TINYBLOB NOT NULL,`
			`modified TIMESTAMP DEFAULT '0000-00-00 00:00:00',`
			`INDEX namelocs (name(255))) ENGINE = MyISAM`
			`PARTITION BY HASH(id) PARTITIONS 2;`
Fix test failure when the mysql-test/ directory is not writable. 2010-11-24 18:51:31 +01:00			`LOAD DATA LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/init_file.txt'`
Bug#51851: Server with SBR locks mutex twice on LOAD DATA into partitioned MyISAM table Problem was that both partitioning and myisam used the same table_share->mutex for different protections (auto inc and repair). Solved by adding a specific mutex for the partitioning auto_increment. Also adding destroying the ha_data structure in free_table_share (which is to be propagated into 5.5). This is a 5.1 ONLY patch, already fixed in 5.5+. 2010-10-01 13:39:04 +02:00			`INTO TABLE t1 (name);`
			`DROP TABLE t1;`