1. 30 Jun, 2005 1 commit
  2. 23 Jun, 2005 1 commit
  3. 08 Jun, 2005 1 commit
    • svoj@mysql.com's avatar
      Fix for · cc31c4c7
      svoj@mysql.com authored
      BUG#10675 - MySQL fails to build with --openssl on Mac OS X 10.4
      BUG#11150 - HP-UX yaSSL/OpenSSL configure/header problem
      Remove obsolete code.
      cc31c4c7
  4. 06 Jun, 2005 1 commit
  5. 03 Jun, 2005 5 commits
    • mronstrom@mysql.com's avatar
      Bug #10901 · 1eaacaf1
      mronstrom@mysql.com authored
      After review fix
      Copy from internal state to share state only when in lock write
      mode (happens only when lock table x write has been performed since
      update_state_info is only called when holding a TL_READ_NO_INSERT
      lock normally. Previous patch would have failed in combination with
      delayed writes.
      1eaacaf1
    • mronstrom@mysql.com's avatar
      Bug #10901 · 96252c1d
      mronstrom@mysql.com authored
      Analyze table corrupts the state on
      data_file_length, records, index_file_length...
      by writing the shared state when there is an updated internal
      state due to inserts or deletes
      Fixed by synching the shared state with the internal state before
      writing it to disk
      Added test cases of 2 error cases and a normal case in new
      analyze test case
      96252c1d
    • serg@serg.mylan's avatar
      Merge bk-internal:/home/bk/mysql-4.0/ · 52340c55
      serg@serg.mylan authored
      into serg.mylan:/usr/home/serg/Abk/mysql-4.0
      52340c55
    • serg@serg.mylan's avatar
      *don't* mess with kernel defines, boy. · f55a378e
      serg@serg.mylan authored
      and HAVE_ATOMIC_ADD/HAVE_ATOMIC_SUB is tested in configure
      f55a378e
    • ndbdev@dl145b.mysql.com's avatar
      sql_repl.cc: · 25cb1423
      ndbdev@dl145b.mysql.com authored
        Bug #11064  	some read error not detected in replication on 64-bit platform
      25cb1423
  6. 01 Jun, 2005 1 commit
  7. 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
  8. 26 May, 2005 2 commits
  9. 25 May, 2005 1 commit
  10. 18 May, 2005 2 commits
  11. 15 May, 2005 2 commits
  12. 14 May, 2005 1 commit
  13. 13 May, 2005 2 commits
  14. 11 May, 2005 1 commit
  15. 09 May, 2005 1 commit
  16. 08 May, 2005 4 commits
  17. 07 May, 2005 8 commits
  18. 06 May, 2005 3 commits
  19. 29 Apr, 2005 1 commit
  20. 28 Apr, 2005 1 commit
    • 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