1. 01 Aug, 2006 8 commits
  2. 31 Jul, 2006 1 commit
  3. 29 Jul, 2006 2 commits
  4. 28 Jul, 2006 4 commits
  5. 26 Jul, 2006 2 commits
    • kroki/tomash@moonlight.intranet's avatar
      BUG#21206: memory corruption when too many cursors are opened at once · 4e845ccc
      kroki/tomash@moonlight.intranet authored
      Too many cursors (more than 1024) could lead to memory corruption.
      This affects both, stored routines and C API cursors, and the
      threshold is per-server, not per-connection.  Similarly, the
      corruption could happen when the server was under heavy load
      (executing more than 1024 simultaneous complex queries), and this is
      the reason why this bug is fixed in 4.1, which doesn't support
      cursors.
      
      The corruption was caused by a bug in the temporary tables code, when
      an attempt to create a table could lead to a write beyond allocated
      space.  Note, that only internal tables were affected (the tables
      created internally by the server to resolve the query), not tables
      created with CREATE TEMPORARY TABLE.  Another pre-condition for the
      bug is TRUE value of --temp-pool startup option, which, however, is a
      default.
      
      The cause of a bug was that random memory was overwritten in
      bitmap_set_next() due to out-of-bound memory access.
      4e845ccc
    • aivanov@mysql.com's avatar
      Applied innodb-4.1-ss32 snapshot. · 765ed29c
      aivanov@mysql.com authored
      765ed29c
  6. 24 Jul, 2006 5 commits
  7. 23 Jul, 2006 1 commit
  8. 20 Jul, 2006 1 commit
  9. 19 Jul, 2006 2 commits
  10. 18 Jul, 2006 3 commits
  11. 17 Jul, 2006 2 commits
  12. 15 Jul, 2006 1 commit
  13. 14 Jul, 2006 5 commits
  14. 13 Jul, 2006 3 commits