mirror of
https://github.com/MariaDB/server.git
synced 2025-02-13 17:05:35 +01:00
9ba18d1aa0
- Innochecksum misinterprets the freed pages as active one. This leads the user to think there are too many valid pages exist. - To avoid this confusion, innochecksum introduced one more option --skip-freed-pages and -r to avoid the freed pages while dumping or printing the summary of the tablespace. - Innochecksum can safely assume the page is freed if the respective extent doesn't belong to a segment and marked as freed in XDES_BITMAP in extent descriptor page. - Innochecksum shouldn't assume that zero-filled page as extent descriptor page. Reviewed-by: Marko Mäkelä
10 lines
472 B
Text
10 lines
472 B
Text
SET GLOBAL INNODB_FILE_PER_TABLE= 0;
|
|
CREATE TABLE t1(f1 INT NOT NULL)ENGINE=InnoDB;
|
|
INSERT INTO t1 VALUES(1);
|
|
DROP TABLE t1;
|
|
SET GLOBAL innodb_fast_shutdown=0;
|
|
# Run the innochecksum to display undo log pages
|
|
FOUND 1 /Undo page state: 0 active, [0-9]+ cached, [0-9]+ to_purge, [0-9]+ prepared, [0-9]+ other/ in result.log
|
|
# Run the innochecksum with --skip-freed-pages
|
|
FOUND 1 /Undo page state: 0 active, 0 cached, 0 to_purge, 0 prepared, 0 other/ in result.log
|
|
# restart
|