Commits

Author Commit Message Labels Comments Date
Greg Hurrell
Fix (cosmetic) typos in dict.h
Salvatore Sanfilippo
Merge pull request #693 from ghurrell/dict-h-typos Fix (cosmetic) typos in dict.h
Schuster
redis-check-dump now understands dumps produced by Redis 2.6 (Commit message from @antirez as it was missign in the original commits, also the patch was modified a bit to still work with 2.4 dumps and to avoid if expressions that are always true due to checked types range) This commit changes redis-check-dump to account for new encodings and for the new MSTIME expire format. It also refactors the test for valid type into a function. The code is still comp…
Schuster
redis-check-dump now understands dumps produced by Redis 2.6 (Commit message from @antirez as it was missign in the original commits, also the patch was modified a bit to still work with 2.4 dumps and to avoid if expressions that are always true due to checked types range) This commit changes redis-check-dump to account for new encodings and for the new MSTIME expire format. It also refactors the test for valid type into a function. The code is still comp…
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Default memory limit for 32bit instanced moved from 3.5 GB to 3 GB. In some system, notably osx, the 3.5 GB limit was too far and not able to prevent a crash for out of memory. The 3 GB limit works better and it is still a lot of memory within a 4 GB theorical limit so it's not going to bore anyone :-) This fixes issue #711
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Default memory limit for 32bit instanced moved from 3.5 GB to 3 GB. In some system, notably osx, the 3.5 GB limit was too far and not able to prevent a crash for out of memory. The 3 GB limit works better and it is still a lot of memory within a 4 GB theorical limit so it's not going to bore anyone :-) This fixes issue #711
antirez
Differentiate SCRIPT KILL error replies. When calling SCRIPT KILL currently you can get two errors: * No script in timeout (busy) state. * The script already performed a write. It is useful to be able to distinguish the two errors, but right now both start with "ERR" prefix, so string matching (that is fragile) must be used. This commit introduces two different prefixes. -NOTBUSY and -UNKILLABLE respectively to reply with an error wh…
antirez
Differentiate SCRIPT KILL error replies. When calling SCRIPT KILL currently you can get two errors: * No script in timeout (busy) state. * The script already performed a write. It is useful to be able to distinguish the two errors, but right now both start with "ERR" prefix, so string matching (that is fragile) must be used. This commit introduces two different prefixes. -NOTBUSY and -UNKILLABLE respectively to reply with an error wh…
NanXiao
Update src/redis-benchmark.c The code of current implementation: if (c->pending == 0) clientDone(c); In clientDone function, the c's memory has been freed, then the loop will continue: while(c->pending). The memory of c has been freed now, so c->pending is invalid (c is an invalid pointer now), and this will cause memory dump in some platforams(eg: Solaris). So I think the code should be modified as: if (c->pending == 0) { …
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Fix MULTI / EXEC rendering in MONITOR output. Before of this commit it used to be like this: MULTI EXEC ... actual commands of the transaction ... Because after all that is the natural order of things. Transaction commands are queued and executed *only after* EXEC is called. However this makes debugging with MONITOR a mess, so the code was modified to provide a coherent output. What happens is that MULTI is rendered in the MONITOR output …
antirez
Fix MULTI / EXEC rendering in MONITOR output. Before of this commit it used to be like this: MULTI EXEC ... actual commands of the transaction ... Because after all that is the natural order of things. Transaction commands are queued and executed *only after* EXEC is called. However this makes debugging with MONITOR a mess, so the code was modified to provide a coherent output. What happens is that MULTI is rendered in the MONITOR output …
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Merge remote-tracking branch 'origin/2.6' into 2.6
antirez
Allow AUTH when Redis is busy because of timedout Lua script. If the server is password protected we need to accept AUTH when there is a server busy (-BUSY) condition, otherwise it will be impossible to send SHUTDOWN NOSAVE or SCRIPT KILL. This fixes issue #708.
antirez
Allow AUTH when Redis is busy because of timedout Lua script. If the server is password protected we need to accept AUTH when there is a server busy (-BUSY) condition, otherwise it will be impossible to send SHUTDOWN NOSAVE or SCRIPT KILL. This fixes issue #708.
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
Salvatore Sanfilippo
Merge pull request #707 from NanXiao/patch-1 Update src/redis-benchmark.c
NanXiao
Update src/redis-benchmark.c The code of current implementation: if (c->pending == 0) clientDone(c); In clientDone function, the c's memory has been freed, then the loop will continue: while(c->pending). The memory of c has been freed now, so c->pending is invalid (c is an invalid pointer now), and this will cause memory dump in some platforams(eg: Solaris). So I think the code should be modified as: if (c->pending ==…
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
CONTRIBUTING file updated.
antirez
CONTRIBUTING file updated.
antirez
Redis 2.6.0 RC8 (2.5.14)
Tags
2.6.0-rc8
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
dvir volk
fixed server install script to rewrite the default configuration file and not a template, and removed the old config template Conflicts: utils/redis.conf.tpl
Salvatore Sanfilippo
Merge pull request #544 from dvirsky/2.6 fixed install script to rewrite the default config
bitbucket
Merge branch 'unstable' of https://github.com/antirez/redis into unstable
antirez
Hash function switched to murmurhash2. The previously used hash function, djbhash, is not secure against collision attacks even when the seed is randomized as there are simple ways to find seed-independent collisions. The new hash function appears to be safe (or much harder to exploit at least) in this case, and has better distribution. Better distribution does not always means that's better. For instance in a fast benchmark with "DE…
  1. Prev
  2. Next