------------------------------------------------------------
revno: 4007
committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com>
branch nick: mysql-5.1.70-release
timestamp: Mon 2013-05-13 15:26:11 +0200
message:
  Merging the changes for Build failure issues from mysql-5.1
------------------------------------------------------------
revno: 4006
committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com>
branch nick: mysql-5.1.70-release
timestamp: Mon 2013-05-13 15:22:49 +0200
message:
  Merging the changes for build failures in windows.
------------------------------------------------------------
revno: 4005
committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com>
branch nick: mysql-5.1.70-release
timestamp: Fri 2013-05-10 15:27:03 +0200
message:
  Merging the changes which fixes the build issue for Windows Builds.
  Description:
   Fixing a build issue.  The function innobase_convert_to_system_charset()
   is included only in the builtin InnoDB, and it is missed in InnoDB
   plugin.  Adding this function in InnoDB plugin as well.
------------------------------------------------------------
revno: 4004
committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com>
branch nick: mysql-5.1.70-release
timestamp: Tue 2013-05-07 09:14:51 +0200
message:
  Updated spec file to ignore upgrade error message
------------------------------------------------------------
revno: 4003
committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com>
branch nick: mysql-5.1.70-release
timestamp: Tue 2013-05-07 08:10:09 +0200
message:
  Merging the changes from 5.1 branch to release branch.
  Includes bug fixes for:
  Bug #16722314 FOREIGN KEY ID MODIFIED DURING EXPORT
  Bug #16754901 PARS_INFO_FREE NOT CALLED IN DICT_CREATE_ADD_FOREIGN_TO_DICTIONARY
------------------------------------------------------------
revno: 4002
tags: clone-5.1.70-build
committer: michael.izioumtchenko@oracle.com
branch nick: mysql_src_c2s3
timestamp: Tue 2013-04-30 20:39:12 +0200
message:
  Bug#16405422 - RECOVERY FAILURE, ASSERT !RECV_NO_LOG_WRITE
  
  eliminate a race condition over recv_sys->n_addrs which might result in a database corruption
  in recovery, without reporting a recovery error.
  
  recv_recover_page_func(): move the code segment that decrements recv_sys->n_addrs
    to the end of the function, after the call to mtr_commit()
  
  rb://2282 approved by Inaam
------------------------------------------------------------
revno: 4001
committer: Neeraj Bisht <neeraj.x.bisht@oracle.com>
branch nick: 5.1
timestamp: Tue 2013-04-30 22:38:34 +0530
message:
  BUG#16222245 - CRASH WITH EXPLAIN FOR A QUERY WITH LOOSE SCAN FOR 
  GROUP BY, MYISAM 
  
  Problem:-
  In a query, where we are using loose index scan optimization and 
  we have MIN() causes segmentation fault(where table row length 
  is less then key_length).
  
  Analysis:
  
  While using loose index scan for MIN(), we call key_copy(), to copy 
  the key data from record.
  This function is using temporary record buffer to store key data 
  from the record buffer.But in case where the key length is greater 
  then the buffer length, this will cause a segmentation fault.
  
  
  Solution:
  Give a proper buffer to store a key record.
------------------------------------------------------------
revno: 4000
committer: Sujatha Sivakumar <sujatha.sivakumar@oracle.com>
branch nick: Bug14324766_mysql-5.1
timestamp: Wed 2013-04-24 13:31:10 +0530
message:
  Bug#14324766:PARTIALLY WRITTEN INSERT STATEMENT IN BINLOG
  NO ERRORS REPORTED
        
  Fixing a post push test script failure.
------------------------------------------------------------
revno: 3999
committer: Annamalai Gurusami <annamalai.gurusami@oracle.com>
branch nick: mysql-5.1
timestamp: Wed 2013-04-24 08:47:30 +0200
message:
  Bug #15973904 INNODB PARTITION CODE HOLDS LOCK_OPEN AND SLEEPS WHILE 
  OPENING MISSING PARTITION
  
  In the ha_innobase::open() call, for normal tables, there is no retry logic.
  But for partitioned tables, there is a retry logic introduced as fix for:
  
  http://bugs.mysql.com/bug.php?id=33349  
  https://support.mysql.com/view.php?id=21080
  
  The Bug#33349, does not provide sufficient information to analyze the original
  problem.  The original problem reported by bug#33349 is also minor (just an
  annoyance and no loss of functionality).  Most importantly, the retry logic
  has been introduced without any associated test case.
  
  So we are removing the retry logic for partitioned tables.  When the original
  problem occurs, a different solution will be explored.
------------------------------------------------------------
revno: 3998
author: murthy.narkedimilli@oracle.com
committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com>
branch nick: mysql-5.1
timestamp: Mon 2013-04-22 14:01:07 +0200
message:
  Merge from mysql-5.1.69-release
------------------------------------------------------------
revno: 3997
tags: mysql-5.1.69
committer: Neeraj Bisht <neeraj.x.bisht@oracle.com>
branch nick: 5.1
timestamp: Sat 2013-04-20 12:28:22 +0530
message:
  Bug#16073689 : CRASH IN ITEM_FUNC_MATCH::INIT_SEARCH 
  
  Problem:
  In query like
  select 1 from .. order by match .. against ...;
  causes a debug assert failue.
  
  Analysis:
  In union type query like
  
  (select * from order by a) order by b;
  or
  (select * from order by a) union (select * from order by b);
  
  We skip resolving of order by a for 1st query and order by of a and b in 
  2nd query.
  
  
  This means that, in case when our order by have Item_func_match class, 
  we skip resolving it.
  But we maintain a ft_func_list and at the time of optimization, when we 
  Perform FULLTEXT search before all regular searches on the bases of the 
  list we call Item_func_match::init_search() which will cause debug assert 
  as the item is not resolved.
  
  
  Solution:
  We will skip execution if the item is not fixed and we will not 
  fix index(Item_func_match::fix_index()) for which 
  Item_func_match::fix_field() is not called so that on later changes 
  we can check the dependency on fix field.
