Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL)
-
None
Description
MySQL 5.7.24 includes the following InnoDB changes:
Not applicable to MariaDB:
Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213 is not applicable, because we already removed the TrxInInnoDB code and trx->lock.start_stmt in MDEV-13935.
Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7 is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix MDEV-14637 did not break SPATIAL INDEX handling.
Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F is a fix for online table rebuild when virtual columns exist and the table is in ROW_FORMAT=REDUNDANT. MDEV-13795/MDEV-14332 in MariaDB blocked the online table rebuild when the table contains indexed virtual columns.
Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA is another fix for online table rebuild when indexed virtual columns exist.
Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in MDEV-11751.
Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL and Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL) affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7.
Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED is a regression caused by a change that I cherry-picked to MariaDB 10.2.8 in a way that is not affected. (MariaDB checks fil_space_t* for NULL before dereferencing it.)
wl#11571 : Deprecate Shared tablespaces in partitioned table and WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables do not apply, because MariaDB does not support CREATE TABLESPACE for InnoDB.
Applicable to MariaDB
Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH will be fixed in MDEV-17541.
Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE will be fixed in MDEV-17545.
Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE() will be fixed in MDEV-17546.
Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES will be fixed in MDEV-17548.
Attachments
Issue Links
- blocks
-
MDEV-18338 Merge new release of InnoDB 5.7.25 to 10.2
-
- Closed
-
- is blocked by
-
MDEV-16850 Merge new release of InnoDB 5.7.23 to 10.2
-
- Closed
-
-
MDEV-17541 KILL QUERY during lock wait in FOREIGN KEY check causes hang
-
- Closed
-
-
MDEV-17545 Predicate lock for SPATIAL INDEX should lock non-matching record
-
- Closed
-
-
MDEV-17546 SPATIAL INDEX should not be allowed for FOREIGN KEY
-
- Closed
-
-
MDEV-17548 Incorrect access to off-page column for indexed virtual column
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is blocked by |
Link |
This issue is blocked by |
Description |
MySQL 5.7.24 includes the following InnoDB changes:
h2. Not applicable to MariaDB: [Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213|https://github.com/mysql/mysql-server/commit/0f796807d1c9290a9518ad1cf714e5fcd00f861f] is not applicable, because we already removed the {{TrxInInnoDB}} code and {{trx->lock.start_stmt}} in [Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7|https://github.com/mysql/mysql-server/commit/af43dc209178dcc0720c9d72935a0863b85b5b5b] is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix [Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F|https://github.com/mysql/mysql-server/commit/70c2357469b2242de0804a9ee80a8b988bc6095f] is a fix for online table rebuild when virtual columns exist and the table is in {{ROW_FORMAT=REDUNDANT}}. [Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA|https://github.com/mysql/mysql-server/commit/b84c64e13633f9c963592e82e92e007a82466f5d] is another fix for online table rebuild when indexed virtual columns exist. [Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA|https://github.com/mysql/mysql-server/commit/94208bcb882860f9f21e1a0d1e600cce268e1203] is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in [Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL|https://github.com/mysql/mysql-server/commit/109fd049379ee6fc23717cf630cf6bccb92acfab] and [Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL)|https://github.com/mysql/mysql-server/commit/39d6b4494d475479105e5f9377999bd3a2a737eb] affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7. [Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED|https://github.com/mysql/mysql-server/commit/f544e3f08a40e3199bdfa198c314a966b79ca1d2] is a regression caused by a change that I [cherry-picked to MariaDB 10.2.8|https://github.com/MariaDB/server/commit/9d57468dde8c84f589a3d763166a9b77d614b2ef] in a way that is not affected. (MariaDB checks {{fil_space_t*}} for {{NULL}} before dereferencing it.) [wl#11571 : Deprecate Shared tablespaces in partitioned table|https://github.com/mysql/mysql-server/commit/e08dee47c930fb4860f0931348140f005ad75f92] and [WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables|https://github.com/mysql/mysql-server/commit/d9732177c7eed58bc4068012ee8e4b632cd5da1e] do not apply, because MariaDB does not support {{CREATE TABLESPACE}} for InnoDB. h2. Applicable to MariaDB [Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE|https://github.com/mysql/mysql-server/commit/365111c590082984dbae42e1d1da28ac3f7fb5bd] fixes an ACID bug for {{SPATIAL INDEX}}. h2. To be determined [Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH|https://github.com/mysql/mysql-server/commit/f7bfaea93dbfd5d1cb4048e021ae1cdfb847b418] occurs because a hard error code is being overwritten by the soft error {{DB_LOCK_WAIT_TIMEOUT}}. It looks like also MySQL 5.6 and MariaDB Server 10.0 are affected. There is no test case. [Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE()|https://github.com/mysql/mysql-server/commit/12bfae0520fff9df6aa870500d5c8378df6a0e4c] blocks {{SPATIAL INDEX}} from being considered for {{FOREIGN KEY}}. Could apply to MariaDB. No test case is included. [Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES|https://github.com/mysql/mysql-server/commit/4ec2158bec73f1582501c4b3e3de250fed9edc9a] is a fix for virtual columns. Probably applies to MariaDB. A test case is included. [A follow-up commit|https://github.com/mysql/mysql-server/commit/fa25ffde2cd5effcc9b2668b78b9c4f71b6b3aff] removes the test case. |
MySQL 5.7.24 includes the following InnoDB changes:
h2. Not applicable to MariaDB: [Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213|https://github.com/mysql/mysql-server/commit/0f796807d1c9290a9518ad1cf714e5fcd00f861f] is not applicable, because we already removed the {{TrxInInnoDB}} code and {{trx->lock.start_stmt}} in [Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7|https://github.com/mysql/mysql-server/commit/af43dc209178dcc0720c9d72935a0863b85b5b5b] is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix [Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F|https://github.com/mysql/mysql-server/commit/70c2357469b2242de0804a9ee80a8b988bc6095f] is a fix for online table rebuild when virtual columns exist and the table is in {{ROW_FORMAT=REDUNDANT}}. [Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA|https://github.com/mysql/mysql-server/commit/b84c64e13633f9c963592e82e92e007a82466f5d] is another fix for online table rebuild when indexed virtual columns exist. [Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA|https://github.com/mysql/mysql-server/commit/94208bcb882860f9f21e1a0d1e600cce268e1203] is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in [Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL|https://github.com/mysql/mysql-server/commit/109fd049379ee6fc23717cf630cf6bccb92acfab] and [Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL)|https://github.com/mysql/mysql-server/commit/39d6b4494d475479105e5f9377999bd3a2a737eb] affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7. [Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED|https://github.com/mysql/mysql-server/commit/f544e3f08a40e3199bdfa198c314a966b79ca1d2] is a regression caused by a change that I [cherry-picked to MariaDB 10.2.8|https://github.com/MariaDB/server/commit/9d57468dde8c84f589a3d763166a9b77d614b2ef] in a way that is not affected. (MariaDB checks {{fil_space_t*}} for {{NULL}} before dereferencing it.) [wl#11571 : Deprecate Shared tablespaces in partitioned table|https://github.com/mysql/mysql-server/commit/e08dee47c930fb4860f0931348140f005ad75f92] and [WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables|https://github.com/mysql/mysql-server/commit/d9732177c7eed58bc4068012ee8e4b632cd5da1e] do not apply, because MariaDB does not support {{CREATE TABLESPACE}} for InnoDB. h2. Applicable to MariaDB [Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH|https://github.com/mysql/mysql-server/commit/f7bfaea93dbfd5d1cb4048e021ae1cdfb847b418] will be fixed in [Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE|https://github.com/mysql/mysql-server/commit/365111c590082984dbae42e1d1da28ac3f7fb5bd] fixes an ACID bug for {{SPATIAL INDEX}}. h2. To be determined [Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE()|https://github.com/mysql/mysql-server/commit/12bfae0520fff9df6aa870500d5c8378df6a0e4c] blocks {{SPATIAL INDEX}} from being considered for {{FOREIGN KEY}}. Could apply to MariaDB. No test case is included. [Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES|https://github.com/mysql/mysql-server/commit/4ec2158bec73f1582501c4b3e3de250fed9edc9a] is a fix for virtual columns. Probably applies to MariaDB. A test case is included. [A follow-up commit|https://github.com/mysql/mysql-server/commit/fa25ffde2cd5effcc9b2668b78b9c4f71b6b3aff] removes the test case. |
Link |
This issue is blocked by |
Link |
This issue is blocked by |
Description |
MySQL 5.7.24 includes the following InnoDB changes:
h2. Not applicable to MariaDB: [Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213|https://github.com/mysql/mysql-server/commit/0f796807d1c9290a9518ad1cf714e5fcd00f861f] is not applicable, because we already removed the {{TrxInInnoDB}} code and {{trx->lock.start_stmt}} in [Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7|https://github.com/mysql/mysql-server/commit/af43dc209178dcc0720c9d72935a0863b85b5b5b] is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix [Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F|https://github.com/mysql/mysql-server/commit/70c2357469b2242de0804a9ee80a8b988bc6095f] is a fix for online table rebuild when virtual columns exist and the table is in {{ROW_FORMAT=REDUNDANT}}. [Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA|https://github.com/mysql/mysql-server/commit/b84c64e13633f9c963592e82e92e007a82466f5d] is another fix for online table rebuild when indexed virtual columns exist. [Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA|https://github.com/mysql/mysql-server/commit/94208bcb882860f9f21e1a0d1e600cce268e1203] is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in [Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL|https://github.com/mysql/mysql-server/commit/109fd049379ee6fc23717cf630cf6bccb92acfab] and [Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL)|https://github.com/mysql/mysql-server/commit/39d6b4494d475479105e5f9377999bd3a2a737eb] affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7. [Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED|https://github.com/mysql/mysql-server/commit/f544e3f08a40e3199bdfa198c314a966b79ca1d2] is a regression caused by a change that I [cherry-picked to MariaDB 10.2.8|https://github.com/MariaDB/server/commit/9d57468dde8c84f589a3d763166a9b77d614b2ef] in a way that is not affected. (MariaDB checks {{fil_space_t*}} for {{NULL}} before dereferencing it.) [wl#11571 : Deprecate Shared tablespaces in partitioned table|https://github.com/mysql/mysql-server/commit/e08dee47c930fb4860f0931348140f005ad75f92] and [WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables|https://github.com/mysql/mysql-server/commit/d9732177c7eed58bc4068012ee8e4b632cd5da1e] do not apply, because MariaDB does not support {{CREATE TABLESPACE}} for InnoDB. h2. Applicable to MariaDB [Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH|https://github.com/mysql/mysql-server/commit/f7bfaea93dbfd5d1cb4048e021ae1cdfb847b418] will be fixed in [Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE|https://github.com/mysql/mysql-server/commit/365111c590082984dbae42e1d1da28ac3f7fb5bd] fixes an ACID bug for {{SPATIAL INDEX}}. h2. To be determined [Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE()|https://github.com/mysql/mysql-server/commit/12bfae0520fff9df6aa870500d5c8378df6a0e4c] blocks {{SPATIAL INDEX}} from being considered for {{FOREIGN KEY}}. Could apply to MariaDB. No test case is included. [Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES|https://github.com/mysql/mysql-server/commit/4ec2158bec73f1582501c4b3e3de250fed9edc9a] is a fix for virtual columns. Probably applies to MariaDB. A test case is included. [A follow-up commit|https://github.com/mysql/mysql-server/commit/fa25ffde2cd5effcc9b2668b78b9c4f71b6b3aff] removes the test case. |
MySQL 5.7.24 includes the following InnoDB changes:
h2. Not applicable to MariaDB: [Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213|https://github.com/mysql/mysql-server/commit/0f796807d1c9290a9518ad1cf714e5fcd00f861f] is not applicable, because we already removed the {{TrxInInnoDB}} code and {{trx->lock.start_stmt}} in [Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7|https://github.com/mysql/mysql-server/commit/af43dc209178dcc0720c9d72935a0863b85b5b5b] is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix [Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F|https://github.com/mysql/mysql-server/commit/70c2357469b2242de0804a9ee80a8b988bc6095f] is a fix for online table rebuild when virtual columns exist and the table is in {{ROW_FORMAT=REDUNDANT}}. [Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA|https://github.com/mysql/mysql-server/commit/b84c64e13633f9c963592e82e92e007a82466f5d] is another fix for online table rebuild when indexed virtual columns exist. [Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA|https://github.com/mysql/mysql-server/commit/94208bcb882860f9f21e1a0d1e600cce268e1203] is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in [Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL|https://github.com/mysql/mysql-server/commit/109fd049379ee6fc23717cf630cf6bccb92acfab] and [Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL)|https://github.com/mysql/mysql-server/commit/39d6b4494d475479105e5f9377999bd3a2a737eb] affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7. [Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED|https://github.com/mysql/mysql-server/commit/f544e3f08a40e3199bdfa198c314a966b79ca1d2] is a regression caused by a change that I [cherry-picked to MariaDB 10.2.8|https://github.com/MariaDB/server/commit/9d57468dde8c84f589a3d763166a9b77d614b2ef] in a way that is not affected. (MariaDB checks {{fil_space_t*}} for {{NULL}} before dereferencing it.) [wl#11571 : Deprecate Shared tablespaces in partitioned table|https://github.com/mysql/mysql-server/commit/e08dee47c930fb4860f0931348140f005ad75f92] and [WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables|https://github.com/mysql/mysql-server/commit/d9732177c7eed58bc4068012ee8e4b632cd5da1e] do not apply, because MariaDB does not support {{CREATE TABLESPACE}} for InnoDB. h2. Applicable to MariaDB [Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH|https://github.com/mysql/mysql-server/commit/f7bfaea93dbfd5d1cb4048e021ae1cdfb847b418] will be fixed in [Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE|https://github.com/mysql/mysql-server/commit/365111c590082984dbae42e1d1da28ac3f7fb5bd] will be fixed in [Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE()|https://github.com/mysql/mysql-server/commit/12bfae0520fff9df6aa870500d5c8378df6a0e4c] will be fixed in h2. To be determined [Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES|https://github.com/mysql/mysql-server/commit/4ec2158bec73f1582501c4b3e3de250fed9edc9a] is a fix for virtual columns. Probably applies to MariaDB. A test case is included. [A follow-up commit|https://github.com/mysql/mysql-server/commit/fa25ffde2cd5effcc9b2668b78b9c4f71b6b3aff] removes the test case. |
Link |
This issue is blocked by |
issue.field.resolutiondate | 2018-10-25 14:17:39.0 | 2018-10-25 14:17:39.208 |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Description |
MySQL 5.7.24 includes the following InnoDB changes:
h2. Not applicable to MariaDB: [Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213|https://github.com/mysql/mysql-server/commit/0f796807d1c9290a9518ad1cf714e5fcd00f861f] is not applicable, because we already removed the {{TrxInInnoDB}} code and {{trx->lock.start_stmt}} in [Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7|https://github.com/mysql/mysql-server/commit/af43dc209178dcc0720c9d72935a0863b85b5b5b] is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix [Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F|https://github.com/mysql/mysql-server/commit/70c2357469b2242de0804a9ee80a8b988bc6095f] is a fix for online table rebuild when virtual columns exist and the table is in {{ROW_FORMAT=REDUNDANT}}. [Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA|https://github.com/mysql/mysql-server/commit/b84c64e13633f9c963592e82e92e007a82466f5d] is another fix for online table rebuild when indexed virtual columns exist. [Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA|https://github.com/mysql/mysql-server/commit/94208bcb882860f9f21e1a0d1e600cce268e1203] is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in [Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL|https://github.com/mysql/mysql-server/commit/109fd049379ee6fc23717cf630cf6bccb92acfab] and [Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL)|https://github.com/mysql/mysql-server/commit/39d6b4494d475479105e5f9377999bd3a2a737eb] affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7. [Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED|https://github.com/mysql/mysql-server/commit/f544e3f08a40e3199bdfa198c314a966b79ca1d2] is a regression caused by a change that I [cherry-picked to MariaDB 10.2.8|https://github.com/MariaDB/server/commit/9d57468dde8c84f589a3d763166a9b77d614b2ef] in a way that is not affected. (MariaDB checks {{fil_space_t*}} for {{NULL}} before dereferencing it.) [wl#11571 : Deprecate Shared tablespaces in partitioned table|https://github.com/mysql/mysql-server/commit/e08dee47c930fb4860f0931348140f005ad75f92] and [WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables|https://github.com/mysql/mysql-server/commit/d9732177c7eed58bc4068012ee8e4b632cd5da1e] do not apply, because MariaDB does not support {{CREATE TABLESPACE}} for InnoDB. h2. Applicable to MariaDB [Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH|https://github.com/mysql/mysql-server/commit/f7bfaea93dbfd5d1cb4048e021ae1cdfb847b418] will be fixed in [Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE|https://github.com/mysql/mysql-server/commit/365111c590082984dbae42e1d1da28ac3f7fb5bd] will be fixed in [Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE()|https://github.com/mysql/mysql-server/commit/12bfae0520fff9df6aa870500d5c8378df6a0e4c] will be fixed in h2. To be determined [Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES|https://github.com/mysql/mysql-server/commit/4ec2158bec73f1582501c4b3e3de250fed9edc9a] is a fix for virtual columns. Probably applies to MariaDB. A test case is included. [A follow-up commit|https://github.com/mysql/mysql-server/commit/fa25ffde2cd5effcc9b2668b78b9c4f71b6b3aff] removes the test case. |
MySQL 5.7.24 includes the following InnoDB changes:
h2. Not applicable to MariaDB: [Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213|https://github.com/mysql/mysql-server/commit/0f796807d1c9290a9518ad1cf714e5fcd00f861f] is not applicable, because we already removed the {{TrxInInnoDB}} code and {{trx->lock.start_stmt}} in [Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7|https://github.com/mysql/mysql-server/commit/af43dc209178dcc0720c9d72935a0863b85b5b5b] is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix [Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F|https://github.com/mysql/mysql-server/commit/70c2357469b2242de0804a9ee80a8b988bc6095f] is a fix for online table rebuild when virtual columns exist and the table is in {{ROW_FORMAT=REDUNDANT}}. [Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA|https://github.com/mysql/mysql-server/commit/b84c64e13633f9c963592e82e92e007a82466f5d] is another fix for online table rebuild when indexed virtual columns exist. [Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA|https://github.com/mysql/mysql-server/commit/94208bcb882860f9f21e1a0d1e600cce268e1203] is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in [Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL|https://github.com/mysql/mysql-server/commit/109fd049379ee6fc23717cf630cf6bccb92acfab] and [Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL)|https://github.com/mysql/mysql-server/commit/39d6b4494d475479105e5f9377999bd3a2a737eb] affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7. [Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED|https://github.com/mysql/mysql-server/commit/f544e3f08a40e3199bdfa198c314a966b79ca1d2] is a regression caused by a change that I [cherry-picked to MariaDB 10.2.8|https://github.com/MariaDB/server/commit/9d57468dde8c84f589a3d763166a9b77d614b2ef] in a way that is not affected. (MariaDB checks {{fil_space_t*}} for {{NULL}} before dereferencing it.) [wl#11571 : Deprecate Shared tablespaces in partitioned table|https://github.com/mysql/mysql-server/commit/e08dee47c930fb4860f0931348140f005ad75f92] and [WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables|https://github.com/mysql/mysql-server/commit/d9732177c7eed58bc4068012ee8e4b632cd5da1e] do not apply, because MariaDB does not support {{CREATE TABLESPACE}} for InnoDB. h2. Applicable to MariaDB [Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH|https://github.com/mysql/mysql-server/commit/f7bfaea93dbfd5d1cb4048e021ae1cdfb847b418] will be fixed in [Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE|https://github.com/mysql/mysql-server/commit/365111c590082984dbae42e1d1da28ac3f7fb5bd] will be fixed in [Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE()|https://github.com/mysql/mysql-server/commit/12bfae0520fff9df6aa870500d5c8378df6a0e4c] will be fixed in [Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES|https://github.com/mysql/mysql-server/commit/4ec2158bec73f1582501c4b3e3de250fed9edc9a] will be fixed in |
Link |
This issue blocks |
Workflow | MariaDB v3 [ 90233 ] | MariaDB v4 [ 155102 ] |