Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3.1
Description
The purpose of MDEV-12288 is to reset the DB_TRX_ID column when the history is being removed. This is not taking place:
--source include/have_innodb.inc
|
CREATE TABLE t1(a INT PRIMARY KEY, b INT NOT NULL) ENGINE=InnoDB;
|
INSERT INTO t1 VALUES(1,2),(3,4);
|
UPDATE t1 SET b=-3 WHERE a=3;
|
# Initiate a full purge, which should reset all DB_TRX_ID.
|
SET GLOBAL innodb_fast_shutdown=0;
|
--source include/shutdown_mysqld.inc
|
After running this test, the t1.ibd file page 3 will contain nonzero DB_TRX_ID values.
Attachments
Issue Links
- blocks
-
MDEV-13697 DB_TRX_ID is not always reset when the history is removed
- Closed
- causes
-
MDEV-13654 Various crashes due to DB_TRX_ID mismatch in table-rebuilding ALTER TABLE…LOCK=NONE
- Closed
-
MDEV-13820 trx_id_check() fails during row_log_table_apply()
- Closed
- is caused by
-
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC
- Closed
- relates to
-
MDEV-13542 Crashing on a corrupted page is unhelpful
- Closed
-
MDEV-8139 Fix scrubbing
- Closed
-
MDEV-13559 encryption.innodb-redo-badkey failed in buildbot
- Closed