mirror of
https://github.com/MariaDB/server.git
synced 2025-07-30 16:24:05 +03:00
MDEV-24576 Atomic CREATE TABLE
There are a few different cases to consider Logging of CREATE TABLE and CREATE TABLE ... LIKE - If REPLACE is used and there was an existing table, DDL log the drop of the table. - If discovery of table is to be done - DDL LOG create table else - DDL log create table (with engine type) - create the table - If table was created - Log entry to binary log with xid - Mark DDL log completed Crash recovery: - If query was in binary log do nothing and exit - If discoverted table - Delete the .frm file -else - Drop created table and frm file - If table was dropped, write a DROP TABLE statement in binary log CREATE TABLE ... SELECT required a little more work as when one is using statement logging the query is written to the binary log before commit is done. This was fixed by adding a DROP TABLE to the binary log during crash recovery if the ddl log entry was not closed. In this case the binary log will contain: CREATE TABLE xxx ... SELECT .... DROP TABLE xxx; Other things: - Added debug_crash_here() functionality to Aria to be able to test crash in create table between the creation of the .MAI and the .MAD files.
This commit is contained in:
@ -39,9 +39,10 @@ stop slave 'master1';
|
||||
|
||||
--let $datadir = `SELECT @@datadir`
|
||||
|
||||
let read_master_log_pos=`select $binlog_start_pos + 599`;
|
||||
let relay_log_pos=`select 2*$binlog_start_pos + 643`;
|
||||
let relay_log_space=`select 3*$binlog_start_pos + 705`;
|
||||
let read_master_log_pos=`select $binlog_start_pos + 608`;
|
||||
let relay_log_pos=`select 2*$binlog_start_pos + 652`;
|
||||
let relay_log_space=`select 3*$binlog_start_pos + 714`;
|
||||
|
||||
--replace_result $SERVER_MYPORT_1 MYPORT_1 $read_master_log_pos <read_master_log_pos> $relay_log_pos <relay_log_pos> $relay_log_space <relay_log_space>
|
||||
show slave 'master1' status;
|
||||
--list_files $datadir mysqld*
|
||||
|
Reference in New Issue
Block a user