An error occurred fetching the project authors.
  1. 25 May, 2009 4 commits
  2. 21 May, 2009 1 commit
  3. 20 May, 2009 18 commits
  4. 19 May, 2009 9 commits
  5. 18 May, 2009 3 commits
  6. 14 May, 2009 2 commits
    • vasil's avatar
      branches/zip: · 5c2c89e3
      vasil authored
      Add ChangeLog entry for r4994.
      5c2c89e3
    • marko's avatar
      branches/zip: Merge revisions 4976:4994 from branches/5.1: · bc48ebd8
      marko authored
        ------------------------------------------------------------------------
        r4994 | marko | 2009-05-14 15:04:55 +0300 (Thu, 14 May 2009) | 18 lines
      
        branches/5.1: Prevent a race condition in innobase_commit() by ensuring
        that innodb_commit_concurrency>0 remains constant at run time. (Bug #42101)
      
        srv_commit_concurrency: Make this a static variable in ha_innodb.cc.
      
        innobase_commit_concurrency_validate(): Check that innodb_commit_concurrency
        is not changed from or to 0 at run time.  This is needed, because
        innobase_commit() assumes that innodb_commit_concurrency>0 remains constant.
        Without this limitation, the checks for innodb_commit_concurrency>0
        in innobase_commit() should be removed and that function would have to
        acquire and release commit_cond_m at least twice per invocation.
        Normally, innodb_commit_concurrency=0, and introducing the mutex operations
        would mean significant overhead.
      
        innodb_bug42101.test, innodb_bug42101-nonzero.test: Test cases.
      
        rb://123 approved by Heikki Tuuri
        ------------------------------------------------------------------------
      bc48ebd8
  7. 13 May, 2009 2 commits
    • vasil's avatar
      branches/zip: · f42bc56e
      vasil authored
      Add ChangeLog entry for r4977.
      f42bc56e
    • marko's avatar
      branches/zip: Merge revisions 4746:4976 from branches/5.1: · 6ec131d6
      marko authored
        ------------------------------------------------------------------------
        r4976 | marko | 2009-05-13 15:44:54 +0300 (Wed, 13 May 2009) | 6 lines
      
        branches/5.1: Display DB_ROLL_PTR in the COLUMNS section of the
        innodb_table_monitor output.  It was accidentally omitted due to an
        off-by-one loop condition.  (Bug #44320)
      
        rb://116 approved by Heikki Tuuri
        ------------------------------------------------------------------------
      6ec131d6
  8. 29 Apr, 2009 1 commit
    • marko's avatar
      branches/zip: Distinguish temporary tables in MLOG_FILE_CREATE. · bd237c4b
      marko authored
      This addresses Mantis Issue #23 in InnoDB Hot Backup and some
      of MySQL Bug #41609.
      
      In MLOG_FILE_CREATE, we need to distinguish temporary tables, so that
      InnoDB Hot Backup can work correctly.  It turns out that we can do this
      easily, by using a bit of the previously unused parameter for page number.
      (The page number parameter of MLOG_FILE_CREATE has been written as 0 
      ever since MySQL 4.1, which introduced MLOG_FILE_CREATE.)
      
      MLOG_FILE_FLAG_TEMP: A flag for indicating a temporary table in
      the page number parameter of MLOG_FILE_ operations.
      
      fil_op_write_log(): Add the parameter log_flags.
      
      fil_op_log_parse_or_replay(): Add the parameter log_flags.
      Do not replay MLOG_FILE_CREATE when MLOG_FILE_FLAG_TEMP is set in log_flags.
      This only affects ibbackup --apply-log.  InnoDB itself never replays file
      operations.
      
      rb://117 approved by Heikki Tuuri
      bd237c4b