Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.11, 10.1.0, 10.2.0, 10.3.0
Description
When MySQL 5.6.10 introduced innodb_read_only mode, it skipped the creation of the InnoDB buffer pool dump/restore subsystem in that mode. Attempts to set the variable innodb_buf_pool_dump_now would have no effect in innodb_read_only mode, but the corresponding condition was forgotten in from the other two update functions.
MySQL 5.7.20 would fix the innodb_buffer_pool_load_now, but not innodb_buffer_pool_load_abort.
Attachments
Issue Links
- relates to
-
MDEV-14085 Merge new release of InnoDB MySQL 5.7.20 to 10.2
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Fix Version/s | 10.0.33 [ 22552 ] | |
Fix Version/s | 10.1.29 [ 22636 ] | |
Fix Version/s | 10.2.10 [ 22615 ] | |
Fix Version/s | 10.0 [ 16000 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Fix Version/s | 10.3.3 [ 22644 ] |
Workflow | MariaDB v3 [ 83065 ] | MariaDB v4 [ 153001 ] |