1. 27 Sep, 2011 3 commits
  2. 26 Sep, 2011 10 commits
    • Tor Didriksen's avatar
      local merge · 9cc04425
      Tor Didriksen authored
      9cc04425
    • Tor Didriksen's avatar
      Bug#12985030 SIMPLE QUERY WITH DECIMAL NUMBERS LEAKS MEMORY · 0b706e54
      Tor Didriksen authored
      Re-write the test, to make pushbuild green.
      Workaraound for broken pow() function on:
      SunOS tyr40 5.10 Generic_127112-05 i86pc i386 i86pc
      
      (dbx) where
      current thread: t@1
      =>[1] Item_func_pow::val_real(this = 0x238af20) (optimized), at 0xaa8d13 (line ~1980) in "item_func.cc"
      
      (dbx) print pow(1.01, 1.0)
      pow(1.01, 1) = 1.01
      (dbx) print pow(1.01, 10.0)
      pow(1.01, 10) = 1.1046221254112
      (dbx) print pow(1.01, 100.0)
      pow(1.01, 100) = 2.7048138294215
      (dbx) print pow(1.01, 1000.0)
      pow(1.01, 1000) = 20959.155637814
      (dbx) print pow(1.01, 10000.0)
      pow(1.01, 10000) = 1.635828711189e+43
      (dbx) print pow(1.01, 100000.0)
      pow(1.01, 100000) = Infinity
      (dbx) print pow(1.01, 1000000.0)
      pow(1.01, 1000000) = Infinity
      (dbx) print pow(1.01, 10000000.0)
      pow(1.01, 10000000) = Infinity
      (dbx) print pow(1.01, 100000000.0)
      pow(1.01, 100000000) = Infinity
      (dbx) print pow(1.01, 1000000000.0)
      pow(1.01, 1000000000) = 0.0
      (dbx) print pow(1.01, 10000000000.0)
      pow(1.01, 10000000000) = 0.0
      
      (dbx) print value
      value = 1.0111111111111
      (dbx) print val2
      val2 = 8796093022207.0
      
      (dbx) print pow(value, val2)
      pow(value, val2) = 0.0
      
      so it seems pow(1.01, y)
      returns Infinity for large y, but then starts to return 0.0 for even larger values of y.
      
      0b706e54
    • Bjorn Munch's avatar
      null upmerge · 3952f6bf
      Bjorn Munch authored
      3952f6bf
    • Bjorn Munch's avatar
      merge from 5.5-mtr · 825081b3
      Bjorn Munch authored
      825081b3
    • Bjorn Munch's avatar
      merge from 5.1-mtr · 147f897d
      Bjorn Munch authored
      147f897d
    • Bjorn Munch's avatar
    • Bjorn Munch's avatar
      null upmerge · 5ed1f306
      Bjorn Munch authored
      5ed1f306
    • Bjorn Munch's avatar
      merge from 5.5 main · abbc47f5
      Bjorn Munch authored
      abbc47f5
    • Bjorn Munch's avatar
      merge from 5.1 main · 031b52c4
      Bjorn Munch authored
      031b52c4
    • Marko Mäkelä's avatar
      Merge mysql-5.1 to mysql-5.5. · cbde5cb8
      Marko Mäkelä authored
      cbde5cb8
  3. 23 Sep, 2011 2 commits
  4. 22 Sep, 2011 1 commit
  5. 21 Sep, 2011 5 commits
    • Tor Didriksen's avatar
      Bug#12985030 SIMPLE QUERY WITH DECIMAL NUMBERS LEAKS MEMORY · f9b064a4
      Tor Didriksen authored
      Extra fix: 'if (p5 < p5_a + P5A_MAX)' is not portable.
      p5 starts out pointing to a static array, then may point
      to a buffer on the stack, then may point to malloc()ed memory.
      f9b064a4
    • Daniel Fischer's avatar
      post-merge fix · 8e56eb58
      Daniel Fischer authored
      8e56eb58
    • Daniel Fischer's avatar
      merge from 5.5.16 · 7450044e
      Daniel Fischer authored
      7450044e
    • unknown's avatar
      Bug 12963823 - Crash in Purge thread under unusual circumstances. · d27d267e
      unknown authored
      The problem occurred when indexes are added between the time that an
      UNDO record is created and the time that the purge thread comes around
      and deletes the old secondary index entries.  The purge thread would
      hit an assert when trying to build a secondary index entry for
      searching.  The problem was that the old value of those fields were not
      in the UNDO record since they were not part of an index when the UPDATE
      occured. 
      A test case was added to innodb-index.test.
      d27d267e
    • unknown's avatar
      Bug 12963823 - Crash in Purge thread under unusual circumstances. · 265737d1
      unknown authored
      The problem occurred when indexes are added between the time that an
      UNDO record is created and the time that the purge thread comes around
      and deletes the old secondary index entries.  The purge thread would
      hit an assert when trying to build a secondary index entry for
      searching.  The problem was that the old value of those fields were not
      in the UNDO record since they were not part of an index when the UPDATE
      occured. 
      A test case was added to innodb-index.test.
      265737d1
  6. 20 Sep, 2011 6 commits
  7. 19 Sep, 2011 4 commits
  8. 16 Sep, 2011 4 commits
    • Rafal Somla's avatar
      Update of auth_rpl test. · c388e9c4
      Rafal Somla authored
      For some reason the test authentication plugin accepted connection with arbitrary password. But the intention of the plugin is that password should equal to the authentication string and in the later versions of the server connection fails if password is wrong. So I have updated auth_rpl test to specify the correct password.
      c388e9c4
    • Sergey Vojtovich's avatar
      Merge. · cb9e23bb
      Sergey Vojtovich authored
      cb9e23bb
    • Sergey Vojtovich's avatar
      Merge. · a33b4214
      Sergey Vojtovich authored
      a33b4214
    • Sergey Vojtovich's avatar
      BUG#11761180 - 53646: MYISAMPACK CORRUPTS TABLES WITH · 3f9cbd77
      Sergey Vojtovich authored
                     FULLTEXT INDEXES
      
      myisamchk may create incorrect fulltext index for compressed
      tables. Incorrect data pointer size was used while creating
      fulltext index.
      
      mysql-test/r/myisampack.result:
        A test case for BUG#11761180.
      mysql-test/t/myisampack.test:
        A test case for BUG#11761180.
      storage/myisam/ft_boolean_search.c:
        rec_reflength on share may have adjustments required for
        compressed tables and must be used instead of rec_reflength
        on base info.
      storage/myisam/ft_nlq_search.c:
        rec_reflength on share may have adjustments required for
        compressed tables and must be used instead of rec_reflength
        on base info.
      storage/myisam/mi_check.c:
        rec_reflength on share may have adjustments required for
        compressed tables and must be used instead of rec_reflength
        on base info.
      storage/myisam/mi_write.c:
        rec_reflength on share may have adjustments required for
        compressed tables and must be used instead of rec_reflength
        on base info.
      3f9cbd77
  9. 15 Sep, 2011 5 commits