[MDEV-18897] InnoDB indexes are inconsistent with what defined in .frm for table Created: 2019-03-12  Updated: 2019-03-17  Resolved: 2019-03-17

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.4.3
Fix Version/s: 10.4.4

Type: Bug Priority: Major
Reporter: vasilii chernov Assignee: Sachin Setiya (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

Docker version: 17.06.0-ce, build 02c1d87
MariaDB version: mysqld 10.4.3-MariaDB-1:10.4.3+maria~bionic


Attachments: Text File docker_inspect.txt     Text File maria_crash_log.log    
Issue Links:
Problem/Incident
is caused by MDEV-371 Unique indexes for blobs Closed
Relates
relates to MDEV-18799 Long unique does not work after faile... Closed

 Description   

STR
1. Execute in console

create table host
(
	id int not null
		primary key,
	name varchar(20) null
);
 
create table client
(
	id int not null
		primary key,
	name varchar(20) null,
	host_id int null,
	constraint id_name_idx1_u
		unique (id, name) using hash,
	constraint client_ibfk_1
		foreign key (host_id) references host (id)
);
 
create index host_id
	on client (host_id);

Expected:
Index created

Actual:
Server crash. My IDE shows me

[08] (conn=9) unexpected end of stream, read 0 bytes from 4 (socket was closed by server) java.io.EOFException: unexpected end of stream, read 0 bytes from 4 (socket was closed by server)

Logs in maria_crash_log.log & docker_inspect.txt



 Comments   
Comment by Elena Stepanova [ 2019-03-12 ]

Thanks for the report. The problem seems to have been fixed by the patch for MDEV-18799 (not pushed yet), but I'm assigning it to sachin.setiya.007 anyway to make sure that this or some other fix properly covers it.

Generated at Thu Feb 08 08:47:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.