InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. (Bug #12704861)
Friday, November 18, 2011
Great work, bug #12704861 was fixed!
MySQL Community Server 5.1.60 has been released and I am very happy because the release notes state that bug #12704861 has been fixed. I know this bug quite well. As my readers are very busy let me provide all of the details that have been made available to the community:
Subscribe to:
Post Comments (Atom)
Posts
Soon we might not even have patches as the launchpad trees aren't being updated.
ReplyDeleteFrom https://code.launchpad.net/~mysql/mysql-server/trunk the last update was Nov 2. Is a 2 week gap not normal?
ReplyDeleteIt used to be more often.
ReplyDeleteThe Lunchpad stopped being updated quite some time ago. The last tree is 5.1.58 and ~mysql/mysql-server/mysql-trunk says:
ReplyDelete"This branch may be out of date, because Launchpad has not been able to access it since 2011-09-10."
I wrote to Keith Larson on Sep 19 but I did not receive any response. :-(
There was a lag a few months back, then that was resolved. This looks like a new issue. Guess it is time to change focus -- maybe MongoDB.
ReplyDeleteI looked into the commit messages: http://www.mysqlperformanceblog.com/2011/11/20/bug12704861/
ReplyDelete@RME, that is incorrect, few days back I built mysql from source using that tree and it was 5.6.4.
ReplyDelete@Mark, the tree is updated now. Just pulled it, have to merge now. I think Stewart also posted on mysql list about tree not updated. They seem to have responded.