Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
N/A
-
None
Description
From https://github.com/mysql/mysql-server
|
+ 551338af241...8d1dd573901 5.7 -> origin/5.7 (forced update)
|
+ 1bfe02bdad6...e57893fef5b 8.0 -> origin/8.0 (forced update)
|
+ 84ef2cea3ee...4325596603f cluster-7.4 -> origin/cluster-7.4 (forced update)
|
+ 97e108f10e5...2400ba6fbef cluster-7.5 -> origin/cluster-7.5 (forced update)
|
+ 4956fa44719...9c357485159 cluster-7.6 -> origin/cluster-7.6 (forced update)
|
* [new tag] mysql-5.7.42 -> mysql-5.7.42
|
* [new tag] mysql-8.0.33 -> mysql-8.0.33
|
* [new tag] mysql-cluster-7.5.30 -> mysql-cluster-7.5.30
|
* [new tag] mysql-cluster-7.6.26 -> mysql-cluster-7.6.26
|
* [new tag] mysql-cluster-8.0.33 -> mysql-cluster-8.0.33
|
Because there was a force-push to the branches, I had to figure out a creative way of finding the changes:
git diff -I'Copyright \(c\).*Oracle' mysql-5.7.41..mysql-5.7.42 storage/innobase/
|
This returns only 31 lines, all corresponding to the following change:
Not applicable to MariaDB Server
Bug#34750489: applying a updated online log may access out-of-bounds memory
If I change the send OPTIMIZE TABLE t1 in the test case to the following, it will fail because MariaDB will refuse the operation:
SET debug_sync = 'alter_table_update_log signal send_concurrent WAIT_FOR concurrent_done'; |
ALTER TABLE t1 FORCE, LOCK=NONE, ALGORITHM=INPLACE; |
mysqltest: At line 31: query 'ALTER TABLE t1 FORCE, LOCK=NONE, ALGORITHM=INPLACE' failed: ER_ALTER_OPERATION_NOT_SUPPORTED (1845): ALGORITHM=INPLACE is not supported for this operation. Try ALGORITHM=COPY
|
In MariaDB 10.2.11 (which was released in November 2017) we addressed MDEV-13795 and MDEV-14332 by refusing online ALTER TABLE rebuild when indexed virtual columns would have to be evaluated while applying the log.
Attachments
Issue Links
- blocks
-
MDEV-31620 Q3 2023 release merge
-
- Closed
-
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-