1. 01 Mar, 2010 18 commits
  2. 27 Feb, 2010 1 commit
  3. 26 Feb, 2010 20 commits
    • Georgi Kodinov's avatar
      merge 5.0-bugteam -> 5.1-bugteam · 5927a233
      Georgi Kodinov authored
      5927a233
    • Georgi Kodinov's avatar
      merge · 4c3005c7
      Georgi Kodinov authored
      4c3005c7
    • Alexey Kopytov's avatar
      Null merge of the InnoDB snapshot from mysql-5.1-bugteam · eaeef7c6
      Alexey Kopytov authored
      to mysql-trunk-merge.
      eaeef7c6
    • Alexey Kopytov's avatar
      Manual merge from mysql-5.1-bugteam to mysql-trunk-merge. · 8266ebbe
      Alexey Kopytov authored
      Conflicts:
      
      Text conflict in scripts/Makefile.am
      Text conflict in sql/share/Makefile.am
      8266ebbe
    • Georgi Kodinov's avatar
      Bug #51468: mysqld_multi is broken in 5.1.44 · cc188fb9
      Georgi Kodinov authored
      Fixed a syntax error in mysqld_multi.sh
      cc188fb9
    • Sergey Vojtovich's avatar
      Merge innodb-5.1-ss6765 to 5.1-bugteam. · f476f83b
      Sergey Vojtovich authored
      f476f83b
    • Sergey Glukhov's avatar
      automerge · 80303d7e
      Sergey Glukhov authored
      80303d7e
    • Sergey Glukhov's avatar
      Bug#50995 Having clause on subquery result produces incorrect results. · 7fd2461c
      Sergey Glukhov authored
      The problem is that cond->fix_fields(thd, 0) breaks
      condition(cuts off 'having'). The reason of that is
      that NULL valued Item pointer is present in the
      middle of Item list and it breaks the Item processing
      loop.
      
      
      mysql-test/r/having.result:
        test case
      mysql-test/t/having.test:
        test case
      sql/item_cmpfunc.h:
        added ASSERT to make sure that we do not add NULL valued Item pointer
      sql/sql_select.cc:
        skip adding an item to condition if Item pointer is NULL.
        skip adding a list to condition if this list is empty.
      7fd2461c
    • Evgeny Potemkin's avatar
      Auto-merged fox for the bug#50843. · 97e5e12a
      Evgeny Potemkin authored
      97e5e12a
    • Evgeny Potemkin's avatar
      Bug#50843: Filesort used instead of clustered index led to · 09d5f8b7
      Evgeny Potemkin authored
      performance degradation.
      
      Filesort + join cache combination is preferred to full index scan because it
      is usually faster. But it's not the case when the index is clustered one.
      
      Now test_if_skip_sort_order function prefers filesort only if index isn't
      clustered.
      
      mysql-test/r/innodb_mysql.result:
        Added a test case for the bug#50843.
      mysql-test/t/innodb_mysql.test:
        Added a test case for the bug#50843.
      sql/sql_select.cc:
        Bug#50843: Filesort used instead of clustered index led to
        performance degradation.
        Now test_if_skip_sort_order function prefers filesort only if index isn't
        clustered.
      09d5f8b7
    • Alexander Nozdrin's avatar
      Auto-merge from mysql-next-mr. · c518659a
      Alexander Nozdrin authored
      c518659a
    • Sergey Vojtovich's avatar
      Applying InnoDB snapshot, fixes BUG#50691 · 27384521
      Sergey Vojtovich authored
      Detailed revision comments:
      
      r6669 | jyang | 2010-02-11 12:24:19 +0200 (Thu, 11 Feb 2010) | 7 lines
      branches/5.1: Fix bug #50691, AIX implementation of readdir_r
      causes InnoDB errors. readdir_r() returns an non-NULL value
      in the case of reaching the end of a directory. It should
      not be treated as an error return.
      
      rb://238 approved by Marko
      27384521
    • Sergey Vojtovich's avatar
      Applying InnoDB snapshot, fixes BUG#38901 · 572a1bf2
      Sergey Vojtovich authored
      Detailed revision comments:
      
      r6613 | inaam | 2010-02-09 20:23:09 +0200 (Tue, 09 Feb 2010) | 11 lines
      branches/5.1: Fix Bug #38901
      InnoDB logs error repeatedly when trying to load page into buffer pool
      
      In buf_page_get_gen() if we are unable to read a page (because of
      corruption or some other reason) we keep on retrying. This fills up
      error log with millions of entries in no time and we'd eventually run
      out of disk space. This patch limits the number of attempts that we
      make (currently set to 100) and after that we abort with a message.
      
      rb://241 Approved by: Heikki
      572a1bf2
    • Sergey Vojtovich's avatar
      Applying InnoDB snapshot, fixes BUG#49001 · ca05a2cf
      Sergey Vojtovich authored
      Detailed revision comments:
      
      r6545 | jyang | 2010-02-03 03:57:32 +0200 (Wed, 03 Feb 2010) | 8 lines
      branches/5.1: Fix bug #49001, "SHOW INNODB STATUS deadlock info
      incorrect when deadlock detection aborts". Print the correct
      lock owner when recursive function lock_deadlock_recursive()
      exceeds its maximum depth LOCK_MAX_DEPTH_IN_DEADLOCK_CHECK.
      
      rb://217, approved by Marko.
      ca05a2cf
    • Sergey Vojtovich's avatar
      Applying InnoDB snapshot · c1974784
      Sergey Vojtovich authored
      Detailed revision comments:
      
      r6538 | sunny | 2010-01-30 00:43:06 +0200 (Sat, 30 Jan 2010) | 6 lines
      branches/5.1: Check *first_value every time against the column max
      value and  set *first_value to next autoinc if it's > col max value.
      ie.  not rely on what is passed in from MySQL.
      
      [49497] Error 1467 (ER_AUTOINC_READ_FAILED) on inserting a negative value
      rb://236
      c1974784
    • Sergey Vojtovich's avatar
      Applying InnoDB snapshot · 36fc6536
      Sergey Vojtovich authored
      Detailed revision comments:
      
      r6537 | sunny | 2010-01-30 00:35:00 +0200 (Sat, 30 Jan 2010) | 2 lines
      branches/5.1: Undo r6536.
      36fc6536
    • Sergey Vojtovich's avatar
      Applying InnoDB snapshot · 1c7350df
      Sergey Vojtovich authored
      Detailed revision comments:
      
      r6536 | sunny | 2010-01-30 00:13:42 +0200 (Sat, 30 Jan 2010) | 6 lines
      branches/5.1: Check *first_value everytime against the column max
      value and  set *first_value to next autoinc if it's > col max value.
      ie.  not rely on what is passed in from MySQL.
      
      [49497] Error 1467 (ER_AUTOINC_READ_FAILED) on inserting a negative value
      rb://236
      1c7350df
    • Sergey Vojtovich's avatar
      Applying InnoDB snapshot · 78a5c0ca
      Sergey Vojtovich authored
      Detailed revision comments:
      
      r6535 | sunny | 2010-01-30 00:08:40 +0200 (Sat, 30 Jan 2010) | 11 lines
      branches/5.1: Undo the change from r6424. We need to return DB_SUCCESS even
      if we were unable to initialize the tabe autoinc value. This is required for
      the open to succeed. The only condition we currently treat as a hard error
      is if the autoinc field instance passed in by MySQL is NULL.
      
      Previously if the table autoinc value was 0 and the next value was requested
      we had an assertion that would fail. Change that assertion and treat a value
      of 0 to mean that the autoinc system is unavailable. Generation of next
      value will now return failure.
      
      rb://237
      78a5c0ca
    • Alexander Barkov's avatar
      After-fix for WL#2649 Number-to-string conversion. · 13cb3ac4
      Alexander Barkov authored
      This change fixes test failure for partition_repair_myisam
      and partition_recover_myisam.
      
      The problem was that:
      - the file std_data/corrupt_crash.MYI
        contains charsetnr=63 (binary) for index segments.
      - the new .frm file contains charsetnr=8 (latin1) for
        the same segments.
      As a result REPAIR refused to repair frm+MYI files
      with different segment definition.
      
      This fix restores the old behavior for frm and MYI files:
      they now store charsetnr=63 for numeric/datetime data types.
      13cb3ac4
    • Alexander Nozdrin's avatar
      f83a40b0
  4. 25 Feb, 2010 1 commit