1. 04 Feb, 2015 1 commit
  2. 29 Jan, 2015 1 commit
  3. 28 Jan, 2015 1 commit
  4. 23 Jan, 2015 1 commit
  5. 19 Jan, 2015 5 commits
  6. 16 Jan, 2015 2 commits
  7. 14 Jan, 2015 3 commits
  8. 13 Jan, 2015 3 commits
  9. 10 Jan, 2015 1 commit
  10. 06 Jan, 2015 1 commit
    • Kristian Nielsen's avatar
      MDEV-7189: main.processlist fails sporadically in buildbot · 00649525
      Kristian Nielsen authored
      The test case tried to trigger a DEBUG_SYNC point at the end of a SELECT
      SLEEP(5) statement. It did this by using EXECUTE 2, intending to trigger first
      at the end of SET DEBUG_SYNC, and second at the end of the SELECT SLEEP(5).
      
      However, in --ps-protocol mode, this does not work, because the SELECT is
      executed in two steps (Prepare followed by Execute). Thus, the DEBUG_SYNC got
      triggered too early, during the Prepare stage rather than Execute, and the
      test case could race and information_schema.processlist see the thread in the
      wrong state.
      
      This patch fixes by changing the way the DEBUG_SYNC point is triggered. Now we
      add a DBUG injection inside the code for SLEEP(5). This ensures that the
      DEBUG_SYNC point is not activated until the SLEEP(5) is running, ensuring
      that the following wait for completion will be effective.
      00649525
  11. 04 Jan, 2015 2 commits
  12. 02 Jan, 2015 3 commits
  13. 28 Dec, 2014 2 commits
  14. 23 Dec, 2014 1 commit
  15. 22 Dec, 2014 1 commit
  16. 21 Dec, 2014 6 commits
  17. 19 Dec, 2014 4 commits
  18. 18 Dec, 2014 2 commits
    • Sergey Petrunya's avatar
      Merge 5.3 -> 5.5 · 13e1acc5
      Sergey Petrunya authored
      13e1acc5
    • Sergey Petrunya's avatar
      MDEV-6830: Server crashes in best_access_path after a sequence of SELECTs ... · b75090c7
      Sergey Petrunya authored
      generate_derived_keys_for_table() did not work correctly in the case where
      - it had a potential index on derived table
      - however, TABLE::check_tmp_key() would disallow creation of this index 
        after looking at its future key parts (because of the key parts exceeding 
        max. index length)
      - the code would leave a KEYUSE structure that refers to a non-existant index.
        Depending on further optimizer calculations, this could cause a crash. 
      b75090c7