1. 14 Jun, 2016 5 commits
  2. 13 Jun, 2016 2 commits
  3. 12 Jun, 2016 3 commits
  4. 10 Jun, 2016 3 commits
  5. 08 Jun, 2016 5 commits
  6. 24 May, 2016 5 commits
  7. 16 May, 2016 2 commits
    • Sujatha Sivakumar's avatar
      Bug#23251517: SEMISYNC REPLICATION HANGING · ef3f09f0
      Sujatha Sivakumar authored
      Revert following bug fix:
      
      Bug#20685029: SLAVE IO THREAD SHOULD STOP WHEN DISK IS
      FULL
      Bug#21753696: MAKE SHOW SLAVE STATUS NON BLOCKING IF IO
      THREAD WAITS FOR DISK SPACE
      
      This fix results in a deadlock between slave IO thread
      and SQL thread.
      
      (cherry picked from commit e3fea6c6dbb36c6ab21c4ab777224560e9608b53)
      ef3f09f0
    • Shishir Jaiswal's avatar
      Bug#21977380 - POSSIBLE BUFFER OVERFLOW ISSUES · 9d72fb4a
      Shishir Jaiswal authored
      DESCRIPTION
      ===========
      Buffer overflow is reported in a lot of code sections
      spanning across server, client programs, Regex libraries
      etc. If not handled appropriately, they can cause abnormal
      behaviour.
      
      ANALYSIS
      ========
      The reported casea are the ones which are likely to result
      in SEGFAULT, MEMORY LEAK etc.
      
      FIX
      ===
      - sprintf() has been replaced by my_snprintf() to avoid
      buffer overflow.
      - my_free() is done after checking if the pointer isn't
        NULL already and setting it to NULL thereafter at few
        places.
      - Buffer is ensured to be large enough to hold the data.
      - 'unsigned int' (aka 'uint') is replaced with 'size_t'
      to avoid wraparound.
      - Memory is freed (if not done so) after its alloced and
      used.
      - Inserted assert() for size check in InnoDb memcached
      code (from 5.6 onwards)
      - Other minor changes
      
      (cherry picked from commit 3487e20959c940cbd24429afa795ebfc8a01e94f)
      9d72fb4a
  8. 10 May, 2016 1 commit
  9. 29 Apr, 2016 1 commit
  10. 27 Apr, 2016 1 commit
  11. 26 Apr, 2016 3 commits
  12. 25 Apr, 2016 2 commits
  13. 24 Apr, 2016 1 commit
    • Sergey Vojtovich's avatar
      MDEV-9975 - main.partition_innodb_plugin fails sporadically · 2b7573ec
      Sergey Vojtovich authored
      Fixed wait condition to wait for InnoDB to actually acquire row locks instead
      of waiting for thread to enter "Searching rows for update" state (which happens
      earlier).
      
      Also use default wait timeout, 2 seconds can be too few for threads to enter
      appropriate state.
      2b7573ec
  14. 23 Apr, 2016 2 commits
  15. 22 Apr, 2016 4 commits
    • Sergey Vojtovich's avatar
      MDEV-9970 - main.sp-threads fails sporadically · 618e300b
      Sergey Vojtovich authored
      Added proper waiting for thread to enter required state. Also reduced amount of
      information dumped from processlist.
      618e300b
    • Daniel Bartholomew's avatar
      bump the VERSION · bd75ee74
      Daniel Bartholomew authored
      bd75ee74
    • Alexander Barkov's avatar
      MDEV-9372 select 100 between 1 and 9223372036854775808 returns false · 3f0d07e5
      Alexander Barkov authored
      Integer comparison of INT expressions with different signess in BETWEEN
      is not safe. Switching to DECIMAL comparison in case if INT arguments
      have different signess.
      3f0d07e5
    • Nisha Gopalakrishnan's avatar
      BUG#23135731: INSERT WITH DUPLICATE KEY UPDATE REPORTS · 3b6f9aac
      Nisha Gopalakrishnan authored
                    INCORRECT ERROR.
      
      Analysis
      ========
      INSERT with DUPLICATE KEY UPDATE and REPLACE on a table
      where foreign key constraint is defined fails with an
      incorrect 'duplicate entry' error rather than foreign
      key constraint violation error.
      
      As part of the bug fix for BUG#22037930, a new flag
      'HA_CHECK_FK_ERROR' was added while checking for non fatal
      errors to manage FK errors based on the 'IGNORE' flag. For
      INSERT with DUPLICATE KEY UPDATE and REPLACE queries, the
      foreign key constraint violation error was marked as non-fatal,
      even though IGNORE was not set. Hence it continued with the
      duplicate key processing resulting in an incorrect error.
      
      Fix:
      ===
      Foreign key violation errors are treated as non fatal only when
      the IGNORE is not set in the above mentioned queries. Hence reports
      the appropriate foreign key violation error.
      3b6f9aac