~kevincrane-p/mysql-server/5.5 : changes

~kevincrane-p/mysql-server/5.5 » Changes from revision 4047

From Revision 4047 to 4028

Rev	Summary	Authors	Tags	Date
4047	Merge MySQL 5.5.41 Merge MySQL 5.5.41	Kevin Crane		9 years ago
4046	Merge MySQL 5.5.40 Merge MySQL 5.5.40	Kevin Crane		9 years ago
4045	Merge MySQL 5.5.39 Merge MySQL 5.5.39	Inaam Rana		9 years ago
4044	Merge MySQL 5.5.37 Merge MySQL 5.5.37	Inaam Rana		9 years ago
4043	Merge MySQL 5.5.36 Merge MySQL 5.5.36	Liang		10 years ago
4042	Merge MySQL 5.5.35 Merge MySQL 5.5.35	Liang		10 years ago
4041	Merge mysql-5.5.34 local Merge mysql-5.5.34 local	Liang		10 years ago
4040	Merge MySQL 5.5.33 Merge MySQL 5.5.33	Liang		10 years ago
4039	Merge MySQL 5.5.32 Merge MySQL 5.5.32	Liang		10 years ago
4038	Merge MySQL 5.5.31 Merge MySQL 5.5.31	Liang		10 years ago
4037	Merge MySQL 5.5.30. Merge MySQL 5.5.30.	Davi Arnaut		11 years ago
4036	Merge MySQL 5.5.29. Merge MySQL 5.5.29.	Davi Arnaut		11 years ago
4035	Add "packaging/rpm-uln/" directory. Add "packaging/rpm-uln/" directory. Directory "SPECIFIC-ULN/" was removed in the parent revision. Now the directory is added in a new path but with the same file ids.	Davi Arnaut		11 years ago
4034	Relocate directory "SPECIFIC-ULN/ to "packaging/rpm-uln/". Relocate directory "SPECIFIC-ULN/ to "packaging/rpm-uln/". Revision joerg.bruehe@oracle.com-20121108180644-n67cgi9o3lewt99g, which renames the directory "SPECIFIC-ULN/" to "packaging/rpm-uln/" broke the importation of changes from the upstream MySQL bazaar tree to git. The cause of the problem is that the bzr-git plugin, which is used to import said changes, does not properly handle directories being renamed (see Launchpad Bug#818318). In this case, the import succeeds but ends up creating a broken tree. In order to work around this problem, the "SPECIFIC-ULN/" directory is removed and re-added (with same file ids) as "packaging/rpm-uln/" in a later revision. This basically mimics the rename as a remove and add. This way, the bzr-git plugin is able to correctly handle the directory move. From this point on, upstream changes will need to be merged, but this shouldn't cause any conflicts.	Davi Arnaut		11 years ago
4033	merge 5.1 => 5.5 merge 5.1 => 5.5	Tor Didriksen	clone-5.5.29-build	11 years ago
4032	BUG#13556441: CHECK AND REPAIR TABLE SHOULD BE MORE ROBUST [... BUG#13556441: CHECK AND REPAIR TABLE SHOULD BE MORE ROBUST [4] Problem description: mysql server crashes when we run repair table on currupted table. Analysis: The problem with this bug seem to be key_reflength out of bounds (186 according to debugger). We read this value from meta-data segment of .MYI file while doing mi_open(). If you look into _mi_kpointer() you can see that the upper limit for key_reflength is 7. Solution: In mi_open() there is a line like: if (share->base.keystart > 65535 \|\| share->base.rec_reflength > 8) we should verify key_reflength here as well.	Venkata Sidagam		11 years ago
4031	BUG#14485479: Merge into mysql-5.5 branch BUG#14485479: Merge into mysql-5.5 branch	Ashish Agarwal		11 years ago
4030	BUG#11754894: MYISAMCHK ERROR HAS INCORRECT REFERENCE BUG#11754894: MYISAMCHK ERROR HAS INCORRECT REFERENCE TO MYISAM_SORT_BUFFER_SIZE Null Merge from 5.1 to 5.5	Anirudh Mangipudi		11 years ago
4029	BUG#11754894: MYISAMCHK ERROR HAS INCORRECT REFERENCE BUG#11754894: MYISAMCHK ERROR HAS INCORRECT REFERENCE TO 'MYISAM_SORT_BUFFER_SIZE' Merging from 5.1 to 5.5	Anirudh Mangipudi		11 years ago
4028	BUG#14659685: main.mysqlbinlog_row_myisam.test main.mysqlbin... BUG#14659685: main.mysqlbinlog_row_myisam.test main.mysqlbinlog_row_innodb.test are skipped merge from 5.1 into 5.5	Shivji Kumar Jha		11 years ago

Older »