- 06 3月, 2013 7 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This makes programs not checking the return value for NULL much safer since with this change: 1) It is still possible to iterate the zero-length result without crashes. 2) sdssplitargs_free will work against NULL and 0 count.
-
由 antirez 提交于
An empty input string also resulted into the function returning NULL making it harder for the caller to distinguish between error and empty string without checking the original input string length.
-
由 charsyam 提交于
-
由 antirez 提交于
While Redis is loading the AOF or RDB file in memory only a subset of commands are allowed. This commit adds AUTH to this subset.
-
- 04 3月, 2013 4 次提交
-
-
由 antirez 提交于
This should improve things in two ways: 1) Prevent timeouts caused by the execution of long commands. 2) Improve detection of real connection errors. This is mostly effective only on Linux because of the bogus default keepalive settings. In Linux we have OS-specific calls to set the keepalive interval to reasonable values.
-
由 0x20h 提交于
-
由 stamhe 提交于
1) Add a check for aeCreateTimeEvent in function initServer.
-
由 stamhe 提交于
-
- 12 2月, 2013 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Steven Penny 提交于
This makes it readable on GitHub and editors without auto wrapping.
-
- 11 2月, 2013 9 次提交
- 08 2月, 2013 2 次提交
- 05 2月, 2013 7 次提交
-
-
由 antirez 提交于
-
由 charsyam 提交于
Further details from @antirez: It was reported by @StopForumSpam on Twitter that the Redis replication link was strangely using multiple TCP packets for multiple commands. This wastes a lot of bandwidth and is due to the TCP_NODELAY option we enable on the socket after accepting a new connection. However the master -> slave channel is a one-way channel since Redis replication is asynchronous, so there is no point in trying to reduce the latency, we should aim to reduce the bandwidth. For this reason this commit introduces the ability to disable the nagle algorithm on the socket after a successful SYNC. This feature is off by default because the delay can be up to 40 milliseconds with normally configured Linux kernels.
-
由 antirez 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Johan Bergström 提交于
-
由 Rock Li 提交于
If each if conditions are all fail, variable retval will under uninitlized
-
- 04 2月, 2013 2 次提交
-
-
由 David Celis 提交于
Make several edits to the example redis.conf configuration file for improved flow and grammar. Signed-off-by: NDavid Celis <me@davidcel.is>
-
由 Gengliang Wang 提交于
In CASE 2, the call sunionDiffGenericCommand will involve the string "srandmember" > sadd foo one (integer 1) > sadd srandmember two (integer 2) > srandmember foo 3 1)"one" 2)"two"
-
- 23 1月, 2013 1 次提交
-
-
由 antirez 提交于
There was a bug in the previous version of this library that caused a crash under the circumstances described in issue #901. The newer version of the library appears to be fixed (I tested it manually with valgrind and everything seems fine now). For more information about this library please visit this web site: http://www.inf.puc-rio.br/~roberto/struct/
-
- 22 1月, 2013 2 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe the client respectively all the channels and patters if called without arguments. However when these functions are called without arguments, but there are no channels or patters we are subscribed to, the old behavior was to don't reply at all. This behavior is broken, as every command should always reply. Also it is possible that we are no longer subscribed to a channels but we are subscribed to patters or the other way around, and the client should be notified with the correct number of subscriptions. Also it is not pretty that sometimes we did not receive a reply at all in a redis-cli session from these commands, blocking redis-cli trying to read the reply. This fixes issue #714.
-
- 21 1月, 2013 2 次提交
- 19 1月, 2013 1 次提交
-
-
由 antirez 提交于
-