- 14 Jul, 2014 2 commits
-
-
antirez authored
-
michael-grunder authored
Previously, the command definition for the OBJECT command specified a minimum of two args (and that it was variadic), which meant that if you sent this: OBJECT foo When cluster was enabled, it would result in an assertion/SEGFAULT when Redis was attempting to extract keys. It appears that OBJECT is not variadic, and only ever takes 3 args. https://gist.github.com/michael-grunder/25960ce1508396d0d36a
-
- 11 Jul, 2014 1 commit
-
-
antirez authored
-
- 10 Jul, 2014 5 commits
- 09 Jul, 2014 32 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This happens in the child process so we don't care about latency: better to sync metadata as well.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This commit adds both support for redis.conf and CONFIG SET/GET.
-
antirez authored
-
antirez authored
-
antirez authored
It is not a good idea to bloat the code with gettimeofday() calls if the instance is working well, and turning monitoring on at runtime is a joke.
-
antirez authored
-
antirez authored
Instead we update the old sample with the new latency if it is greater.
-
antirez authored
-
antirez authored
-
antirez authored
-