1. 11 Jan, 2007 2 commits
  2. 08 Jan, 2007 1 commit
  3. 03 Jan, 2007 1 commit
  4. 20 Nov, 2006 1 commit
    • tsmith/tim@siva.hindu.god's avatar
      Backport patch of bugfix for: · 45b77b83
      tsmith/tim@siva.hindu.god authored
      - Bug #15815: Very poor performance with multiple queries running concurrently
      - Bug #22868: 'Thread thrashing' with > 50 concurrent conns under an upd-intensive workloadw
      
      This is a patch from an e-mail; it is not included in an InnoDB snapshot.
      45b77b83
  5. 07 Nov, 2006 3 commits
  6. 06 Nov, 2006 2 commits
  7. 17 Oct, 2006 1 commit
  8. 13 Oct, 2006 1 commit
  9. 02 Oct, 2006 1 commit
  10. 29 Sep, 2006 1 commit
  11. 28 Sep, 2006 1 commit
  12. 27 Sep, 2006 1 commit
  13. 23 Sep, 2006 1 commit
  14. 22 Sep, 2006 3 commits
  15. 18 Sep, 2006 1 commit
    • kroki/tomash@moonlight.intranet's avatar
      BUG#9678: Client library hangs after network communication failure · 92610664
      kroki/tomash@moonlight.intranet authored
                (back-port to 4.0)
      
      Socket timeouts in client library were used only on Windows.
      Additionally, in 4.0 write operations erroneously set read timeout.
      
      The solution is to use socket timeouts in client library on all
      systems were they are supported, and to differentiate between read
      and write timeouts.
      
      No test case is provided because it is impossible to simulate network
      failure in current test suite.
      92610664
  16. 15 Sep, 2006 1 commit
  17. 07 Sep, 2006 1 commit
  18. 06 Sep, 2006 1 commit
  19. 31 Aug, 2006 1 commit
  20. 30 Aug, 2006 1 commit
    • cmiller@zippy.cornsilk.net's avatar
      Bug#4053: too many of "error 1236: 'binlog truncated in the middle of \ · 2c356ec7
      cmiller@zippy.cornsilk.net authored
      	event' from master"
      
      Since there is no repeatable test case, and this is obviously wrong, this is
      the most conservative change that might possibly work.  
      
      The syscall  read()  wasn't checked for a negative return value for an
      interrupted read.  The kernel  sys_read()  returns -EINTR, and the "library" 
      layer maps that to return value of -1 and sets  errno  to EINTR.  It's 
      impossible (on Linux) for  read()  to set errno EINTR without the return 
      value being -1 .
      
      So, if we're checking for EINTR behavior, we should not require that the
      return value be zero.
      2c356ec7
  21. 29 Aug, 2006 1 commit
  22. 10 Aug, 2006 1 commit
  23. 29 Jul, 2006 1 commit
  24. 28 Jul, 2006 3 commits
  25. 26 Jul, 2006 1 commit
  26. 24 Jul, 2006 1 commit
  27. 21 Jul, 2006 1 commit
  28. 08 Jul, 2006 1 commit
  29. 07 Jul, 2006 2 commits
  30. 05 Jul, 2006 1 commit
  31. 01 Jul, 2006 1 commit
    • cmiller@zippy.(none)'s avatar
      Bug#19006: 4.0 valgrind problems (in test func_str) · 5039184e
      cmiller@zippy.(none) authored
      On exactly-sized Strings, the String::c_ptr() function peeked beyond the
      end of the buffer, possibly into unititialized space to see whether the 
      buffer was NUL-terminated.
      
      In a place that did peek improperly, we now use a c_ptr_safe() function, 
      which doesn't peek where it shouldn't.
      5039184e