1. 30 Mar, 2010 2 commits
  2. 26 Mar, 2010 1 commit
    • vdimov's avatar
      branches/5.1: · 53c27178
      vdimov authored
      Fix a non-determinism in innodb_bug38231.
      
      Reported by:	Sergey Vojtovich <svoj@Sun.COM>
      53c27178
  3. 15 Mar, 2010 1 commit
    • vasil's avatar
      branches/5.1: · 4fcebfd3
      vasil authored
      Typecast to silence a compiler warning:
      
      row/row0sel.c: 4548
              C4244: '=' : conversion from 'float' to 'ib_ulonglong', possible loss of data
      row/row0sel.c: 4553
              C4244: '=' : conversion from 'double' to 'ib_ulonglong', possible loss of data
      
      Reported by:	Jonas Oreland <Jonas.Oreland@Sun.COM>
      Discussed with:	Sunny Bains <sunny.bains@oracle.com>
      4fcebfd3
  4. 10 Mar, 2010 2 commits
    • vasil's avatar
      branches/5.1: · 83737a34
      vasil authored
      In innodb_bug38231.test: replace the fragile sleep 0.2 that depends on timing
      with a more robust condition which waits for the TRUNCATE and LOCK commands
      to appear in information_schema.processlist. This could also break if there
      are other sessions executing the same SQL commands, but there are none during
      the execution of the mysql test.
      83737a34
    • vasil's avatar
      branches/5.1: · 5eceb6f4
      vasil authored
      Add the missing --reap statements in innodb_bug38231.test. Probably MySQL
      enforced the presence of those recently and the test started failing like:
      
        main.innodb_bug38231                     [ fail ]
                Test ended at 2010-03-10 08:48:32
        
        CURRENT_TEST: main.innodb_bug38231
        mysqltest: At line 49: Cannot run query on connection between send and reap
      5eceb6f4
  5. 09 Mar, 2010 1 commit
  6. 08 Mar, 2010 1 commit
  7. 03 Mar, 2010 1 commit
  8. 11 Feb, 2010 1 commit
  9. 09 Feb, 2010 1 commit
    • inaam's avatar
      branches/5.1: Fix Bug #38901 · 26740944
      inaam authored
      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
      26740944
  10. 03 Feb, 2010 1 commit
  11. 29 Jan, 2010 4 commits
  12. 21 Jan, 2010 3 commits
  13. 15 Jan, 2010 1 commit
  14. 12 Jan, 2010 3 commits
    • marko's avatar
      branches/5.1: In innobase_initialize_autoinc(), do not attempt to read · 04e0ee05
      marko authored
      the maximum auto-increment value from the table if
      innodb_force_recovery is set to at least 4, so that writes are
      disabled. (Bug #46193)
      
      innobase_get_int_col_max_value(): Move the function definition before
      ha_innobase::innobase_initialize_autoinc(), because that function now
      calls this function.
      
      ha_innobase::innobase_initialize_autoinc(): Change the return type to
      void.  Do not attempt to read the maximum auto-increment value from
      the table if innodb_force_recovery is set to at least 4.  Issue
      ER_AUTOINC_READ_FAILED to the client when the auto-increment value
      cannot be read.
      
      rb://144 by Sunny, revised by Marko
      04e0ee05
    • marko's avatar
      branches/5.1: Non-functional change: · cf1356b7
      marko authored
      Make innobase_get_int_col_max_value() a static function.
      It does not access any fields of class ha_innobase.
      cf1356b7
    • jyang's avatar
      branches/5.1: Fix bug #49238: Creating/Dropping a temporary table · e3e3bdcc
      jyang authored
      while at 1023 transactions will cause assert. Handle possible
      DB_TOO_MANY_CONCURRENT_TRXS when deleting metadata in
      row_drop_table_for_mysql().
      
      rb://220, approved by Marko
      e3e3bdcc
  15. 22 Dec, 2009 3 commits
    • marko's avatar
    • marko's avatar
      branches/5.1: lock_print_info_summary(): Remove a reference to · 5b0b143e
      marko authored
      innobase_mysql_end_print_arbitrary_thd() that should have been
      removed in r6347 when removing the function.
      5b0b143e
    • marko's avatar
      branches/5.1: Merge a change from MySQL: · ee656d0b
      marko authored
      ------------------------------------------------------------
      revno: 3236
      committer: Satya B <satya.bn@sun.com>
      branch nick: mysql-5.1-bugteam
      timestamp: Tue 2009-12-01 17:48:57 +0530
      message:
        merge to mysql-5.1-bugteam
          ------------------------------------------------------------
          revno: 3234.1.1
          committer: Gleb Shchepa <gshchepa@mysql.com>
          branch nick: mysql-5.1-bugteam
          timestamp: Tue 2009-12-01 14:38:40 +0400
          message:
            Bug #38883 (reopened): thd_security_context is not thread safe, crashes?
      
            manual merge 5.0-->5.1, updating InnoDB plugin.
          ------------------------------------------------------------
          revno: 1810.3968.13
          committer: Gleb Shchepa <gshchepa@mysql.com>
          branch nick: mysql-5.0-bugteam
          timestamp: Tue 2009-12-01 14:24:44 +0400
          message:
            Bug #38883 (reopened): thd_security_context is not thread safe, crashes?
      
            The bug 38816 changed the lock that protects THD::query from
            LOCK_thread_count to LOCK_thd_data, but didn't update the associated
            InnoDB functions.
      
            1. The innobase_mysql_prepare_print_arbitrary_thd and the
            innobase_mysql_end_print_arbitrary_thd InnoDB functions have been
            removed, since now we have a per-thread mutex: now we don't need to wrap
            several inter-thread access tries to THD::query with a single global
            LOCK_thread_count lock, so we can simplify the code.
      
            2. The innobase_mysql_print_thd function has been modified to lock
            LOCK_thd_data in direct way.
      ee656d0b
  16. 17 Dec, 2009 1 commit
  17. 15 Dec, 2009 1 commit
    • marko's avatar
      branches/5.1: Merge r4922 from branches/zip. · c4cdbe88
      marko authored
      This the fix for the first part of Bug #41609 from InnoDB Plugin to
      the built-in InnoDB in MySQL 5.1. This allows InnoDB Hot Backup to
      back up a database while the built-in InnoDB in MySQL 5.1 is creating
      temporary tables. (This fix does not address the printouts about
      missing .ibd files for temporary tables at InnoDB startup, which was
      committed to branches/zip in r6252.)
      
      rb://219 approved by Sunny Bains.
      
      branches/zip: Distinguish temporary tables in MLOG_FILE_CREATE.
      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.
      c4cdbe88
  18. 14 Dec, 2009 1 commit
  19. 27 Nov, 2009 1 commit
    • vasil's avatar
      branches/5.1: · 3474b4a5
      vasil authored
      Minor changes to support plugin snapshots.
      3474b4a5
  20. 25 Nov, 2009 5 commits
  21. 24 Nov, 2009 1 commit
  22. 20 Nov, 2009 2 commits
  23. 19 Nov, 2009 2 commits