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

InnoDB: Failing assertion: table->n_rec_locks == 0

    XMLWordPrintable

Details

    Description

      I hit during testing on origin/10.6 9aea7d83c8d006519bdf1f3269136b3756ed7548 2022-11-17T08:37:35+02:00
      # 2022-11-18T10:09:01 [2517410] | 2022-11-18 10:08:40 0x7f9f03aec640  InnoDB: Assertion failure in file /data/Server/10.6/storage/innobase/dict/dict0dict.cc line 1862
      # 2022-11-18T10:09:01 [2517410] | InnoDB: Failing assertion: table->n_rec_locks == 0
      when running the following scenario
      1. Start the DB server
      2. Session 1 runs
           CREATE SCHEMA birth ;
          CREATE TABLE birth . parent (
               col1 INT PRIMARY KEY, col_text TEXT,
               col_text_g TEXT GENERATED ALWAYS AS (SUBSTR(col_text,1,499))
          ;         (storage engine is InnoDB)
          CREATE TABLE birth . child LIKE birth . parent ;
          ALTER TABLE birth . child ADD FOREIGN KEY (col1) REFERENCES birth . parent(col1) ;
          RENAME TABLE birth . parent TO test . parent , birth . child TO test . child ;
      3. Session 1 runs a stream of
          INSERT INTO test . child (col1) VALUES ( <random int between 9 and 64 ); COMMIT ;
          Session 2 runs concurrent a stream of
          ALTER TABLE test . parent ADD FULLTEXT ( col_text ) ;
      
      

      Attachments

        1. FK.cfg
          45 kB
          Matthias Leich
        2. REPLAY_SIMP10_RR.sh
          12 kB
          Matthias Leich
        3. table_stress_innodb_fk-micro.yy
          0.7 kB
          Matthias Leich

        Activity

          People

            thiru Thirunarayanan Balathandayuthapani
            mleich Matthias Leich
            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.