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

enforce-storage-engine=InnoDB has no usability as an option to mysqld-install-db

    XMLWordPrintable

    Details

      Description

      Starting mysqld-install-db server setup with --enforce-storage-engine=InnoDB gives:

      2021-08-16 11:45:47 23042769061632 [ERROR] InnoDB: Trying to create a MySQL system table `mysql`.`db` of type InnoDB. MySQL system tables must be of the MyISAM type!
      ERROR: 1005  Can't create table `mysql`.`db` (errno: 168 "Unknown (generic) error from engine")
      2021-08-16 11:45:47 23042925725632 [ERROR] Aborting
      

      Interesting is also the 168 unknown error from InnoDB.

      Perhaps a better way to handle this would be to automatically make system tables MyISAM (without any overwrite possibility). This would also make sense given that a server which already has MyISAM system tables can be started fine with --enforce-storage-engine=InnoDB thereafter, i.e. the "enforce" naming can be misleading in any case.

      Another option is to disable the enforce-storage-engine option (or the InnoDB setting specifically) for mysqld-install-db only.

        Attachments

          Activity

            People

            Assignee:
            marko Marko Mäkelä
            Reporter:
            Roel Roel Van de Paar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration