The b129_SNPMapInfo_36_3.bcp.gz dataset was from the person who first reported this issue to MySQL nearly 3 years ago and was not the data I was having problems with. I did, however, this morning try to replicate his problem from his data and instructions and I got the exact same behavior as he did. I have attached a file of my output, system specs, and my.conf for my system, I hope that will be useful.
I am not sure what else to say. 3 different people on different hardware and linux distros have run into this behavior. I personally have tested mysql5.0, 5.1, 5.5 and mariadb5.1 on SLES 10, 11, and Ubuntu 10.04 and get the exact same behavior every time so I'm pretty sure there is a problem. If there is any other information I can provide please let me know, solving this problem will save me countless hours of processing time.
Alexey,
Thanks for looking into this.
The b129_SNPMapInfo _36_3.bcp. gz dataset was from the person who first reported this issue to MySQL nearly 3 years ago and was not the data I was having problems with. I did, however, this morning try to replicate his problem from his data and instructions and I got the exact same behavior as he did. I have attached a file of my output, system specs, and my.conf for my system, I hope that will be useful.
I am not sure what else to say. 3 different people on different hardware and linux distros have run into this behavior. I personally have tested mysql5.0, 5.1, 5.5 and mariadb5.1 on SLES 10, 11, and Ubuntu 10.04 and get the exact same behavior every time so I'm pretty sure there is a problem. If there is any other information I can provide please let me know, solving this problem will save me countless hours of processing time.