lp:mysql-server/5.5

Created by Mats Kindahl on 2011-10-10 and last modified on 2015-01-22

NOTE: The MySQL Server repositories on Launchpad have been frozen. Future updates will be published on github instead.

Get this branch:
bzr branch lp:mysql-server/5.5
Members of Oracle/MySQL Engineering can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Oracle/MySQL Engineering
Project:
MySQL Server
Status:
Mature

Recent revisions

4736. By Balasubramanian Kandasamy on 2014-11-04

 Added sles11 repo packages

4735. By mithun <email address hidden> on 2014-11-03

Bug #19372926 : 5.5.38 FAILS FUNC_MATH MTR TEST.

Issue :
-------
This seems for some platform -(LONGLONG_MIN) is
not flagged as out of range.

Fix:
----
Fix is backported from mysql-5.6 bug 14314156.
Fixed by adding an explicit test for this value in
Item_func_neg::int_op().

4734. By Marko Makela <email address hidden> on 2014-10-30

Bug#19904003 INNODB_LIMIT_OPTIMISTIC_INSERT_DEBUG=1 CAUSES INFINITE PAGE SPLIT

The debug configuration parameter innodb_optimistic_insert_debug
which was introduced for testing corner cases in B-tree handling
had a bug in it. The value 1 would trigger an infinite sequence
of page splits.

Fix: When the value 1 is specified, disable this debug feature.
Approved by Yasufumi Kinoshita

4733. By mrainb0w on 2014-10-29

Bug #19908343 SERVER CRASHES WHEN EXECUTING ALTER TABLE

Problem:

In the function dict_foreign_remove_from_cache(), the rb tree was updated
without actually verifying whether the given foreign key object is there in the
rb tree or not. There can be an existing foreign key object with the same id
in the rb tree, which must not be removed. Such a scenario comes when an
attempt is made to add a foreign key object with a duplicate identifier.

Solution:

When the foreign key object is removed from the dictionary cache, ensure
that the foreign key object removed from the rbt is the correct one.

rb#7168 approved by Jimmy and Marko.

4732. By Marko Makela <email address hidden> on 2014-10-27

Bug#19584379 Reporting corruption may corrupt the innodb data dictionary

dict_set_corrupted(): Use the canonical way of searching for
less-than-equal (PAGE_CUR_LE) and then checking low_match.

The code that was introduced in MySQL 5.5.17 in
    Bug#11830883 SUPPORT "CORRUPTED" BIT FOR INNODB TABLES AND INDEXES
could position the cursor on the page supremum, and then attempt
to overwrite non-existing 7th field of the 1-field supremum record.

Approved by Jimmy Yang

4731. By Balasubramanian Kandasamy on 2014-10-23

Rpm 4.9 and newer is more strict regarding weekday in %changelog

4730. By Balasubramanian Kandasamy on 2014-10-21

Fix changelog entries build failure

4729. By Balasubramanian Kandasamy on 2014-10-21

Bug#19775856: When the socket option is relative, mysqld startup script fails on CentOS 6

4728. By Arun Kuruvila <email address hidden> on 2014-10-21

Bug #16581605: REPLACE.EXE UTILITY IS BROKEN IN 5.5

Description:- Replace, the string replacement utility fails
on the windows platform.

Analysis:- The utility takes files and multiple string
pairs as input. In the windows platform, the utility maps
the standard input incorrectly (Considers 0 as the fd for
standard input instead of 2048 on windows). Hence when the
input file is supplied to the utility due to the incorrect
mapping, a bad file descriptor error is generated causing
the utility to exit with an error.

Fix:- "my_fileno()" is used for getting the correct file
despscriptor for standard input.

4727. By mrainb0w on 2014-10-20

The test case innodb.foreign-keys is failing in pb2 5.5. This is because
some of the tables are created in InnoDB and some tables are created in MyISAM.
We need to create all tables on InnoDB. Fix is to add engine=innodb to the
CREATE TABLE statements.

approved in IM by Marko and Vasil.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:~dannythefool/+junk/trunk-outdated
This branch contains Public information 
Everyone can see this information.