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

Unnecessary InnoDB warnings upon bootstrap

Details

    Description

      On server bootstrap with default options, InnoDB produces the warnings

      2017-01-23  1:49:05 140688075253632 [Warning] InnoDB: New log files created, LSN=45892
      		 
      2017-01-23  1:49:06 140688075253632 [Warning] InnoDB: Creating foreign key constraint system tables.

      It's bootstrap, naturally InnoDB creates new files and system tables, there should be no warnings of this kind.

      Attachments

        Issue Links

          includes

          Task - A task that needs to be done. MDEV-11782 Redefine the innodb_encrypt_log format

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment -

            The "New log files created" was changed to [Note] in MDEV-11782.

            marko Marko Mäkelä added a comment - The "New log files created" was changed to [Note] in MDEV-11782 .
            marko Marko Mäkelä added a comment -

            I changed the warning about the SYS_FOREIGN and SYS_FOREIGN_COLS creation to a note, and removed some messages about the successful creation of metadata tables, because they are basically noise.

            marko Marko Mäkelä added a comment - I changed the warning about the SYS_FOREIGN and SYS_FOREIGN_COLS creation to a note, and removed some messages about the successful creation of metadata tables, because they are basically noise.

            People

              marko Marko Mäkelä
              elenst Elena Stepanova
              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.