1. 26 Aug, 2014 4 commits
  2. 22 Aug, 2014 2 commits
  3. 21 Aug, 2014 2 commits
  4. 06 Aug, 2014 1 commit
  5. 31 Jul, 2014 1 commit
    • Jan Lindström's avatar
      MDEV-6512: InnoDB: Assertion failure in thread 4537024512 in file · e974b564
      Jan Lindström authored
      buf0buf.cc line 2642.
      
      Analysis: innodb_compression_algorithm is a global variable and
      can change while we are building page compressed page. This could
      lead page corruption.
      
      Fix: Cache innodb_compression_algorithm on local variable before
      doing any compression or page formating to avoid concurrent
      change. Improved page verification on debug builds.
      e974b564
  6. 29 Jul, 2014 1 commit
  7. 25 Jul, 2014 2 commits
    • Jan Lindström's avatar
      Fix compiler error on Windows. · 1f69ff44
      Jan Lindström authored
      1f69ff44
    • Jan Lindström's avatar
      Fiix random test failures on fil_decompress_page_2 function. · 56c4b016
      Jan Lindström authored
      Analysis: InnoDB writes also files that do not contain FIL-header.
      This could lead incorrect analysis on os_fil_read_func function
      when it tries to see is page page compressed based on FIL_PAGE_TYPE
      field on FIL-header. With bad luck uncompressed page that does
      not contain FIL-headed, the byte on FIL_PAGE_TYPE position could
      indicate that page is page comrpessed.
      
      Fix: Upper layer must indicate is file space page compressed
      or not. If this is not yet known, we need to read the FIL-header
      and find it out. Files that we know that are not page compressed
      we can always just provide FALSE.
      56c4b016
  8. 23 Jul, 2014 9 commits
  9. 22 Jul, 2014 2 commits
  10. 05 Jul, 2014 1 commit
  11. 04 Jul, 2014 1 commit
  12. 02 Jul, 2014 1 commit
  13. 29 Jun, 2014 1 commit
  14. 28 Jun, 2014 1 commit
    • Jan Lindström's avatar
      MDEV-6376: InnoDB: Assertion failure in thread 139995225970432 · b35c5912
      Jan Lindström authored
      in file buf0mtflu.cc line 570.
      
      Analysis: Real timing bug, we should take the mutex before we
      try to send those shutdown messages, that would make sure
      that threads doing a unfinished flush (they have acquired
      this mutex) have time to do their work before we add shutdown
      messages to work queue. Currently, we just add those shutdown
      messages to work queue and code assumes that at flush, there
      is constant number of items to be processed and thus
      leading to assertion.
      b35c5912
  15. 27 Jun, 2014 1 commit
  16. 26 Jun, 2014 10 commits