re: could insert...select have problem with corrupt table

[James Black]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Today mysql 4.1.8 has a segmentation fault (signal 11), and crashed.

In the process one table was left corrupted, when it started back up.

An application continued to call insert...select on the corrupted table
as it wasn't realized this happened.

So, in the replication log on the slave we get this error:
050901 10:50:59 [ERROR] Slave: Error 'Duplicate entry '2925542' for key
1' on query. Default database: 'mydb'. Query: 'INSERT INTO
target_table(start,badge,finish,lid,itemtype,rid)SELECT c.start,
c.badge, 1125586211, i.lid, i.itemtype,12576 FROM corrupt_table c,
good_table i WHERE  i.rid=12576 AND c.rid=12576', Error_code: 1062

Could this duplicate record have been caused by my doing an
insert...select from a corrupted table to a good table?

This is on Solaris 9, btw.

Thank you for any clarification.


- --
"Love is mutual self-giving that ends in self-recovery." Fulton Sheen
James Black    james@stripped
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDF1JEikQgpVn8xrARAmaBAJ4jDyW+RdjLBh+tW21PnYR8XRVajwCfbWCV
uQcsbwMY9HKRAa7srzk9TpY=
=FLGE
-----END PGP SIGNATURE-----