- 22 2月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 14 2月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 12 2月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 28 1月, 2013 5 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
When keyspace events are enabled, the overhead is not sever but noticeable, so this commit introduces the ability to select subclasses of events in order to avoid to generate events the user is not interested in. The events can be selected using redis.conf or CONFIG SET / GET.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
- 19 1月, 2013 2 次提交
-
-
由 antirez 提交于
This commit fixes issue #875 that was caused by the following events: 1) There is an active child doing BGSAVE. 2) flushall is called (or any other condition that makes Redis killing the saving child process). 3) An error is sensed by Redis as the child exited with an error (killed by a singal), that stops accepting write commands until a BGSAVE happens to be executed with success. Whitelisting SIGUSR1 and making sure Redis always uses this signal in order to kill its own children fixes the issue.
-
由 guiquanz 提交于
-
- 13 11月, 2012 1 次提交
-
-
由 antirez 提交于
The previous behavior was to return -1 if: 1) Existing key but without an expire set. 2) Non existing key. Now the second case is handled in a different, and TTL will return -2 if the key does not exist at all. PTTL follows the same behavior as well.
-
- 09 11月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 11 9月, 2012 1 次提交
-
-
由 antirez 提交于
Unfortunately we had still the lame atoi() without any error checking in place, so "SELECT foo" would work as "SELECT 0". This was not an huge problem per se but some people expected that DB can be strings and not just numbers, and without errors you get the feeling that they can be numbers, but not the behavior. Now getLongFromObjectOrReply() is used as almost everybody else across the code, generating an error if the number is not an integer or overflows the long type. Thanks to @mipearson for reporting that on Twitter.
-
- 01 5月, 2012 1 次提交
-
-
由 Pieter Noordhuis 提交于
Every matched key in a KEYS call is checked for expiration. When the key is set to expire, the call to `getExpire` will assert that the key also exists in the main dictionary. This in turn causes a rehashing step to be executed. Rehashing a dictionary when there is an iterator active may result in the iterator emitting duplicate entries, or not emitting some entries at all. By using a safe iterator, the rehash step is omitted.
-
- 07 4月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 05 4月, 2012 3 次提交
-
-
由 antirez 提交于
expireGenericCommand(): better variable names and a top-comment that describes the function's behavior.
-
由 Premysl Hruby 提交于
-
由 Premysl Hruby 提交于
-
- 28 3月, 2012 1 次提交
-
-
由 Premysl Hruby 提交于
-
- 27 3月, 2012 1 次提交
-
-
由 Premysl Hruby 提交于
-
- 04 2月, 2012 1 次提交
-
-
由 antirez 提交于
Use less memory when emitting the protocol, by using more shared objects for commonly emitted parts of the protocol.
-
- 02 2月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 30 1月, 2012 1 次提交
-
-
由 antirez 提交于
setKey(): call the higher level wrapper setModifiedKey() instead of touchWatchedKey() even if currently they are exactly the same.
-
- 21 12月, 2011 3 次提交
- 18 11月, 2011 1 次提交
-
-
由 antirez 提交于
New script timeout semantics and SCRIPT KILL implemented. SHUTDOWN NOSAVE and SHUTDOWN SAVE implemented.
-
- 11 11月, 2011 1 次提交
-
-
由 antirez 提交于
high resolution expires API modified to use separated commands. AOF transation to PEXPIREAT of all the expire-style commands fixed.
-
- 10 11月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 09 11月, 2011 2 次提交
-
-
由 antirez 提交于
Initial support for key expire times with millisecond resolution. RDB version is now 3, new opcoded added for high resolution times. Redis is still able to correctly load RDB version 2. Tests passing but still a work in progress. API to specify milliseconds expires still missing, but the precision of normal expires is now already improved and working.
-
由 antirez 提交于
-
- 17 10月, 2011 2 次提交
- 10 10月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 05 10月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 07 7月, 2011 2 次提交
-
-
由 antirez 提交于
don't process EXPIRE with negative TTL or EXPIREAT with time in the past if we are a slave too (see http://groups.google.com/group/redis-db/browse_thread/thread/5a931fefb88b16d5). Also propagate it as DEL.
-
由 Hampus Wessman 提交于
They will be expired (and a DEL will be logged) after the loading is done instead.
-
- 25 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 20 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 06 5月, 2011 1 次提交
-
-
由 antirez 提交于
Fixed semantics of CLUSTER SETSLOT, SELECT now only denied in cluster mode if selected DB is not 0 so that MIGRATE still works well.
-