Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5.1, 10.6.0, 10.7.0
-
None
Description
This line disallows using files bigger than 4G. The correct type should be os_offset_t.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Summary | 32-bit system fails to use big innodb-log-file-size | 32-bit systems fail to use big innodb-log-file-size |
Component/s | Storage Engine - InnoDB [ 10129 ] | |
Fix Version/s | 10.5.14 [ 26809 ] | |
Fix Version/s | 10.6.6 [ 26811 ] | |
Fix Version/s | 10.7.2 [ 26813 ] | |
Assignee | Eugene Kosov [ kevg ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 128028 ] | MariaDB v4 [ 159867 ] |
Affects Version/s | 10.7.0 [ 26072 ] | |
Affects Version/s | 10.6.0 [ 24431 ] | |
Affects Version/s | 10.5.1 [ 24029 ] |
This regression had been introduced in 10.5.1 by this change.
As far as I can tell, an attempt to use innodb_log_file_size larger than 4GiB on a 32-bit system would have resulted in a corrupted (unrecoverable) redo log.
The impact probably is minor, because the log file is rarely configured to be larger than innodb_buffer_pool_size, which is limited to some 2GiB or maybe at most 3GiB on 32-bit systems.