1. 31 May, 2005 1 commit
    • ingo@mysql.com's avatar
      Bug#10224 - ANALYZE TABLE crashing with simultaneous CREATE ... SELECT statement. · 51d80960
      ingo@mysql.com authored
      1.) Added a new option to mysql_lock_tables() for ignoring FLUSH TABLES.
      Used the new option in create_table_from_items().
      It is necessary to prevent the SELECT table from being reopend.
      It would get new storage assigned for its fields, while the
      SELECT part of the command would still use the old (freed) storage.
      2.) Protected the CREATE TABLE and CREATE TABLE ... SELECT commands
      against a global read lock. This prevents a deadlock in
      CREATE TABLE ... SELECT in conjunction with FLUSH TABLES WITH READ LOCK
      and avoids the creation of new tables during a global read lock.
      3.) Replaced set_protect_against_global_read_lock() and
      unset_protect_against_global_read_lock() by
      wait_if_global_read_lock() and start_waiting_global_read_lock()
      in the INSERT DELAYED handling.
      51d80960
  2. 26 May, 2005 2 commits
  3. 25 May, 2005 1 commit
  4. 18 May, 2005 2 commits
  5. 15 May, 2005 2 commits
  6. 14 May, 2005 1 commit
  7. 13 May, 2005 2 commits
  8. 11 May, 2005 1 commit
  9. 09 May, 2005 1 commit
  10. 08 May, 2005 4 commits
  11. 07 May, 2005 8 commits
  12. 06 May, 2005 3 commits
  13. 29 Apr, 2005 1 commit
  14. 28 Apr, 2005 2 commits
    • ingo@mysql.com's avatar
      Bug#8321 - myisampack bug in compression algorithm · 66a158a9
      ingo@mysql.com authored
      This is the second of three changesets. It contains the pure bug fix.
      It also contains the second after-review fixes.
      The problem was that with gcc on x86, shifts are done modulo word size. 
      'value' is 32 bits wide and shifting it by 32 bits is a no-op.
      This was triggered by an evil distribution of character incidences. 
      A distribution of 2917027827 characters made of 202 distinct values led to
      34 occurrences of 32-bit Huffman codes.
      This might have been the first time ever that write_bits() had to write
      32-bit values. Since it can be expected that one day even 32 bits might
      be insufficient, the third changeset suggests to enlarge some variables
      to 64 bits.
      66a158a9
    • jimw@mysql.com's avatar
  15. 27 Apr, 2005 1 commit
  16. 19 Apr, 2005 3 commits
  17. 17 Apr, 2005 1 commit
  18. 15 Apr, 2005 1 commit
  19. 14 Apr, 2005 3 commits