tags 407406 + unreproducible severity normal stop Hello Alexis
On 2007-01-18 Alexis Sukrieh wrote: > Christian Hammers wrote: > > That bug is supposed to be fixed since 5.0.26 if I read it correctly. > > Yep, but I'm facing a symptom very near to the upstream bug reported. > That's why I thought in the first place it was the same bug. I was unable to reproduce the bug with your SQL files. I created a chroot with Debian sarge, there installed MySQL and loaded it with your SQL files and afterwards upgraded the chroot to Debian testing/etch. Both of your queries worked fine in sarge as well as in testing/etch. Maybe your innodb data files were corrupted somewhen else and the problem only just appeared at this occasion. If you try to reproduce it in a second database on your host, e.g. in a chroot so it uses a different inndb table space file, do you get the same error? Until we proved that this is a general problem I downgraded the bugreport as it would prevent 5.0.32 from entering testing/etch. But please try to reproduce it again on your computer, maybe I just did something different. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
