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

ER_KEY_NOT_FOUND upon INSERT into InnoDB table with vector key under READ COMMITTED

    XMLWordPrintable

Details

    Description

      The test case is based on an attempt to load a mariadb-dump dump, foreign_key_checks and unique_checks settings come from there. Only transaction isolation level is a custom setting (originally a startup option). Also reproducible with READ UNCOMMITTED.

      --source include/have_innodb.inc
      		 
       
      		 
      SET unique_checks=0, foreign_key_checks=0;
      		 
      SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;
      		 
       
      		 
      CREATE TABLE t (v VECTOR(1) NOT NULL, VECTOR (v)) ENGINE=InnoDB;
      		 
      INSERT INTO t VALUES (0x31313131),(0x32323232);
      		 
       
      		 
      # Cleanup
      		 
      DROP TABLE t;

      6945a4af85fb8e1af6b36aadde0485645ac6a77e

      		 
      CURRENT_TEST: bug.w4
      		 
      mysqltest: At line 7: query 'INSERT INTO t VALUES (0x31313131),(0x32323232)' failed: ER_KEY_NOT_FOUND (1032): Can't find record in 't'

      Attachments

        Issue Links

          is caused by

          New Feature - A new feature of the product, which has yet to be developed. MDEV-34939 vector search in 11.7

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: