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

"1713: Undo log record is too big" for instant ADD COLUMN with long DEFAULT for BLOB

    XMLWordPrintable

Details

    Description

      The following change to the MDEV-17196 test fails with every innodb_page_size:

      diff --git a/mysql-test/suite/innodb/t/instant_alter.test b/mysql-test/suite/innodb/t/instant_alter.test
      index 720e495e3a7..dc7a56fb641 100644
      --- a/mysql-test/suite/innodb/t/instant_alter.test
      +++ b/mysql-test/suite/innodb/t/instant_alter.test
      @@ -338,8 +338,7 @@ ALGORITHM=INSTANT;
       SET foreign_key_checks=1;
       ALTER TABLE t2 COMMENT 'domestic keys only', DROP FOREIGN KEY fk;
       ALTER TABLE t1 DROP FOREIGN KEY t1_ibfk_1;
      -ALTER TABLE t1 ADD COLUMN big BLOB NOT NULL
      -DEFAULT REPEAT('a', @@GLOBAL.innodb_page_size * .75);
      +ALTER TABLE t1 ADD COLUMN big BLOB NOT NULL DEFAULT REPEAT('a', 65535);
       CHECK TABLE t2, t1;
       DROP TABLE t2, t1;
       
      

      10.3 aba5c72be28cbd3028623070b7bf3d7d1e128be1

      CURRENT_TEST: innodb.instant_alter
      mysqltest: At line 341: query 'ALTER TABLE t1 ADD COLUMN big BLOB NOT NULL DEFAULT REPEAT('a', 65535)' failed: 1713: Undo log record is too big
      

      We seem to be attempting to write the default value to the undo log record.
      Unlike MDEV-17126, it could be possible to fix this without changing the undo log format.

      Work-arounds:

      1. Assign shorter default values
      2. Add , FORCE so that the table will be rebuilt (non-instant operation)

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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