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

Import the tablespace which has descending field index aborts the server

Details

    Description

      Transporting the tablespace from 10.6 to 10.11 version shows the error even
      though table schema matches. (descending order of index fields)

      MariaDB [(none)]> use test;
      Database changed
      MariaDB [test]> create table t1(f1 int not null, f2 int not null, primary key(f1 desc))engine=innodb;
      Query OK, 0 rows affected (0.027 sec)
       
      MariaDB [test]> alter table t1 discard tablespace;
      Query OK, 0 rows affected (0.018 sec)
       
      MariaDB [test]> alter table t1 import tablespace;
      ERROR 1808 (HY000): Schema mismatch (Index PRIMARY field f1 is DESC which does not match with .cfg file)
      

      In other way around,transporting from 10.11 to 10.6, InnoDB ends in crash during
      alter table rebuild operation using inplace algorithm:

       
      MariaDB [test]> alter table t1_pk_desc import tablespace;
      Query OK, 0 rows affected (0.030 sec)
       
      MariaDB [test]> alter table t1_pk_desc force;
      ERROR 2013 (HY000): Lost connection to server during query
       
      mysqld: /home/thiru/source_file/server/10.6/storage/innobase/btr/btr0bulk.cc:173: void PageBulk::insertPage(rec_t*, rec_offs*) [with format <anonymous> = PageBulk::DYNAMIC; rec_t = unsigned char; rec_offs = short unsigned int]: Assertion `cmp_rec_rec(rec, old_rec, offsets, old_offsets, m_index
      
      

      Attachments

        Activity

          There are no comments yet on this issue.

          People

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