Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
N/A
-
None
Description
Note: max_edges_per_node is not important for the scenario, it just allows to achieve the same result with less rows in the table (and thus quicker INSERT).
Still, the test case is non-deterministic, sleep value and the size of the table may need to be adjusted depending on the machine and the build type. Please don't put it into the regression suite, I suppose it should be possible to create a synchronized one instead.
--source include/have_innodb.inc
|
--source include/have_sequence.inc
|
|
|
--let $datadir= `select @@datadir`
|
|
|
create table t (a vector(1) not null) engine=InnoDB; |
insert into t select 0x00000000 from seq_1_to_1000; |
|
|
--connect (con1,localhost,root,,)
|
--send alter table t add vector(a) max_edges_per_node=200
|
|
|
--connection default
|
--sleep 1
|
--let $shutdown_timeout= 0
|
--source include/restart_mysqld.inc
|
|
|
show create table t; |
drop table t; |
--list_files $datadir/test/ |
|
bb-11.6-MDEV-32887-vector 764592a4da2a1b490471732fbefe2ce745ce1f32 |
show create table t;
|
Table Create Table
|
t CREATE TABLE `t` (
|
`a` vector(1) NOT NULL
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci
|
drop table t;
|
#sql-alter-1a7cfc-5#i#00.ibd
|
...
|
MTR's internal check of the test case 'bug.t' failed.
|
...
|
DEBUG_SYNC ON - current signals: ''
|
+#sql-alter-1a7cfc-5#i#00.ibd
|
Attachments
Issue Links
- is caused by
-
MDEV-34939 vector search in 11.7
-
- Closed
-