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

Document Galera Strict DDL

    XMLWordPrintable

    Details

      Description

      Introduced a new wsrep_strict_ddl configuration variable in which
      Galera checks storage engine of the effected table. If table is not
      InnoDB (only storage engine currently fully supporting Galera
      replication) DDL-statement will return error code:

      ER_GALERA_REPLICATION_NOT_SUPPORTED
      eng "DDL-statement is forbidden as table storage engine does not support Galera replication"

      However, when wsrep_replicate_myisam=ON we allow DDL-statements to
      MyISAM tables. If effected table is allowed storage engine Galera
      will run normal TOI.

      This new setting should be for now set globally on all
      nodes in a cluster. When this setting is set following DDL-clauses
      accessing tables not supporting Galera replication are refused:

      • CREATE TABLE (e.g. CREATE TABLE t1(a int) engine=Aria
      • ALTER TABLE
      • TRUNCATE TABLE
      • CREATE VIEW
      • CREATE TRIGGER
      • CREATE INDEX
      • DROP INDEX
      • RENAME TABLE
      • DROP TABLE

      Statements on PROCEDURE, EVENT, FUNCTION are allowed as effected
      tables are known only at execution. Furthermore, USER, ROLE, SERVER,
      DATABASE statements are also allowed as they do not really have
      effected table.

      Release: 10.5.1CS

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              greenman Ian Gilfillan
              Reporter:
              jplindst Jan Lindström
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: