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

Allow --innodb-read-only startup even when change buffer or redo logs are not empty

    XMLWordPrintable

    Details

      Description

      InnoDB refuses read-only startup when the redo log or the change buffer are not empty, issuing the following kind of messages:

      [Warning] InnoDB: innodb_read_only prevents crash recovery
      [ERROR] InnoDB: Change buffer must be empty when --innodb-read-only is set!
      

      We should remove this arbitrary restriction in MariaDB Server.
      It would be entirely possible to apply such changes in the buffer pool, only disabling the writes back to the data files in --innodb-read-only mode.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration