• Sergey Vojtovich's avatar
    Applying InnoDB snapshot · 286dc23a
    Sergey Vojtovich authored
    Detailed revision comments:
    
    r6633 | marko | 2010-02-10 10:40:55 +0200 (Wed, 10 Feb 2010) | 31 lines
    branches/zip: Merge revisions 6538:6613 from branches/5.1:
    
      ------------------------------------------------------------------------
      r6545 | jyang | 2010-02-03 03:57:32 +0200 (Wed, 03 Feb 2010) | 8 lines
      Changed paths:
         M /branches/5.1/lock/lock0lock.c
    
      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.
      ------------------------------------------------------------------------
      r6613 | inaam | 2010-02-09 20:23:09 +0200 (Tue, 09 Feb 2010) | 11 lines
      Changed paths:
         M /branches/5.1/buf/buf0buf.c
         M /branches/5.1/buf/buf0rea.c
         M /branches/5.1/include/buf0rea.h
    
      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
      ------------------------------------------------------------------------
    286dc23a
lock0lock.c 155 KB