Bug #9688 error 127 from table engine if mixing merge and myisam in insert .select from
Submitted: 6 Apr 2005 17:08 Modified: 3 Aug 2005 9:47
Reporter: Martin Friebe (Gold Quality Contributor) (OCA) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.11 OS:Any (*)
Assigned to: Ingo Strüwing CPU Architecture:Any

[6 Apr 2005 17:08] Martin Friebe
Description:
See below, inserting into a table from the table itself works fine as long as it is not hidden behind a merge table.

How to repeat:
CREATE TABLE t1 (a int(11));
CREATE TABLE t2 (a int(11)) ENGINE=MRG_MyISAM UNION=(t1) insert_method=last; 
insert into t1 values (1), (1), (1);

insert into t1 select * from t1;
insert into t2 select * from t2;
insert into t1 select * from t2;
#ERROR 1030 (HY000): Got error 127 from storage engine
insert into t2 select * from t1;
#ERROR 1030 (HY000): Got error 127 from storage engine

drop table t2;
drop table t1;

Suggested fix:
-
[6 Apr 2005 17:09] Martin Friebe
forgot:

perror 127
MySQL error code 127: Record-file is crashed

no operating system error listed
[3 Aug 2005 9:47] Ingo Strüwing
This problem is already addressed by Bug #5390.

A patch for it is already pending, but not yet approved.