Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-27139

32-bit systems fail to use big innodb-log-file-size

Details

    Description

      This line disallows using files bigger than 4G. The correct type should be os_offset_t.

      Attachments

        Activity

          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.

          marko Marko Mäkelä added a comment - 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.

          People

            kevg Eugene Kosov (Inactive)
            kevg Eugene Kosov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.