mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-31 02:51:44 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/suite/innodb/t/log_alter_table.test

48 lines
1.5 KiB
Text
Raw Normal View History

Import and adjust a test from MySQL 5.7.
2017-01-25 16:05:32 +02:00
--source include/have_innodb.inc
--source include/have_debug.inc
# Embedded server does not support crashing
--source include/not_embedded.inc
remove two redundant *.inc files to restart a server namely, restart_mysqld_with_option.inc and kill_and_restart_mysqld.inc - use restart_mysqld.inc instead. Also remove innodb_wl6501_crash_stripped.inc that wasn't used anywhere.
2017-03-12 11:18:51 +01:00
# start afresh
--source include/restart_mysqld.inc
Import and adjust a test from MySQL 5.7.
2017-01-25 16:05:32 +02:00
--echo #
--echo # Bug#21801423 INNODB REDO LOG DOES NOT INDICATE WHEN
--echo # FILES ARE CREATED
--echo #
--echo # Bug#21796691 INNODB REDO LOG DOES NOT INDICATE WHEN
--echo # REDO LOGGING IS SKIPPED
--echo #
--source include/no_checkpoint_start.inc
CREATE TABLE t1 (a INT NOT NULL, b INT UNIQUE) ENGINE=InnoDB;
# MLOG_INDEX_LOAD will not be emitted for empty tables. Insert a row.
INSERT INTO t1 VALUES (1,2);
# We should get two MLOG_INDEX_LOAD for this.
MDEV-19241 InnoDB fails to write MLOG_INDEX_LOAD upon completing ALTER TABLE Similar to what was done in commit aa3f7a107ce3a9a7f80daf3cadd442a61c5493ab for FULLTEXT INDEX, we must ensure that MLOG_INDEX_LOAD records will always be written if redo logging was disabled. row_merge_build_indexes(): Invoke row_merge_write_redo() also when online operation is not being executed or an error occurs. In case of an error, invoke flush_observer->interrupted() so that the pages will not be flushed but merely evicted from the buffer pool. Before resuming redo logging, it is crucial for the correctness of mariabackup and InnoDB crash recovery to flush or evict all affected pages and to write MLOG_INDEX_LOAD records.
2019-04-17 12:46:08 +03:00
ALTER TABLE t1 ADD PRIMARY KEY(a), LOCK=SHARED, ALGORITHM=INPLACE;
Import and adjust a test from MySQL 5.7.
2017-01-25 16:05:32 +02:00
# And one MLOG_INDEX_LOAD for this.
MDEV-19241 InnoDB fails to write MLOG_INDEX_LOAD upon completing ALTER TABLE Similar to what was done in commit aa3f7a107ce3a9a7f80daf3cadd442a61c5493ab for FULLTEXT INDEX, we must ensure that MLOG_INDEX_LOAD records will always be written if redo logging was disabled. row_merge_build_indexes(): Invoke row_merge_write_redo() also when online operation is not being executed or an error occurs. In case of an error, invoke flush_observer->interrupted() so that the pages will not be flushed but merely evicted from the buffer pool. Before resuming redo logging, it is crucial for the correctness of mariabackup and InnoDB crash recovery to flush or evict all affected pages and to write MLOG_INDEX_LOAD records.
2019-04-17 12:46:08 +03:00
ALTER TABLE t1 DROP INDEX b, ADD INDEX (b), LOCK=SHARED;
Import and adjust a test from MySQL 5.7.
2017-01-25 16:05:32 +02:00
--let CLEANUP_IF_CHECKPOINT=DROP TABLE t1;
--source include/no_checkpoint_end.inc
--let $restart_parameters= --debug=d,ib_log
--source include/start_mysqld.inc
let SEARCH_FILE = $MYSQLTEST_VARDIR/log/mysqld.1.err;
let SEARCH_ABORT=NOT FOUND;
search_pattern_in_file.inc changes 1. Special mode to search in error logs: if SEARCH_RANGE is not set, the file is considered an error log and the search is performed since the last CURRENT_TEST: line 2. Number of matches is printed too. "FOUND 5 /foo/ in bar". Use greedy .* at the end of the pattern if number of matches isn't stable. If nothing is found it's still "NOT FOUND", not "FOUND 0". 3. SEARCH_ABORT specifies the prefix of the output. Can be "NOT FOUND" or "FOUND" as before, but also "FOUND 5 " if needed.
2017-03-14 15:36:30 +01:00
# ensure that we have exactly 2 records there.
MDEV-19241 InnoDB fails to write MLOG_INDEX_LOAD upon completing ALTER TABLE Similar to what was done in commit aa3f7a107ce3a9a7f80daf3cadd442a61c5493ab for FULLTEXT INDEX, we must ensure that MLOG_INDEX_LOAD records will always be written if redo logging was disabled. row_merge_build_indexes(): Invoke row_merge_write_redo() also when online operation is not being executed or an error occurs. In case of an error, invoke flush_observer->interrupted() so that the pages will not be flushed but merely evicted from the buffer pool. Before resuming redo logging, it is crucial for the correctness of mariabackup and InnoDB crash recovery to flush or evict all affected pages and to write MLOG_INDEX_LOAD records.
2019-04-17 12:46:08 +03:00
let SEARCH_PATTERN=scan \d+: multi-log rec MLOG_FILE_CREATE2 len \d+ page \d+:0;
Import and adjust a test from MySQL 5.7.
2017-01-25 16:05:32 +02:00
--source include/search_pattern_in_file.inc
search_pattern_in_file.inc changes 1. Special mode to search in error logs: if SEARCH_RANGE is not set, the file is considered an error log and the search is performed since the last CURRENT_TEST: line 2. Number of matches is printed too. "FOUND 5 /foo/ in bar". Use greedy .* at the end of the pattern if number of matches isn't stable. If nothing is found it's still "NOT FOUND", not "FOUND 0". 3. SEARCH_ABORT specifies the prefix of the output. Can be "NOT FOUND" or "FOUND" as before, but also "FOUND 5 " if needed.
2017-03-14 15:36:30 +01:00
# ensure that we have exactly 3 records there.
MDEV-19241 InnoDB fails to write MLOG_INDEX_LOAD upon completing ALTER TABLE Similar to what was done in commit aa3f7a107ce3a9a7f80daf3cadd442a61c5493ab for FULLTEXT INDEX, we must ensure that MLOG_INDEX_LOAD records will always be written if redo logging was disabled. row_merge_build_indexes(): Invoke row_merge_write_redo() also when online operation is not being executed or an error occurs. In case of an error, invoke flush_observer->interrupted() so that the pages will not be flushed but merely evicted from the buffer pool. Before resuming redo logging, it is crucial for the correctness of mariabackup and InnoDB crash recovery to flush or evict all affected pages and to write MLOG_INDEX_LOAD records.
2019-04-17 12:46:08 +03:00
let SEARCH_PATTERN=scan \d+: log rec MLOG_INDEX_LOAD;
Import and adjust a test from MySQL 5.7.
2017-01-25 16:05:32 +02:00
--source include/search_pattern_in_file.inc
CHECK TABLE t1;
# Remove the --debug=d,ib_log setting.
--let $restart_parameters=
--source include/restart_mysqld.inc
DROP TABLE t1;
Reference in a new issue Copy permalink