- 02 5月, 2012 2 次提交
- 01 5月, 2012 3 次提交
-
-
由 Salvatore Sanfilippo 提交于
Use safe dictionary iterator from KEYS (fixes #487)
-
由 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.
-
由 Harmen 提交于
-
- 30 4月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 29 4月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 28 4月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 27 4月, 2012 14 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
An user reported a crash with Redis scripting (see issue #480 on github), inspection of the kindly provided strack trace showed that server.lua_caller was probably set to NULL. The stack trace also slowed that the call to the hook was originating from a point where we just used to set/get a few global variables in the Lua state. What was happening is that we did not set the timeout hook selectively only when the user script was called. Now we set it more selectively, specifically only in the context of the lua_pcall() call, and make sure to remove the hook when the call returns. Otherwise the hook can get called in random contexts every time we do something with the Lua state.
-
由 antirez 提交于
A previous commit removed -g -rdynamic -ggdb as LDFLAGS, not allowing Redis to produce a stack trace wth symbol names on crash. This commit fixes the issue.
-
由 antirez 提交于
-
由 antirez 提交于
This commit reverts most of c5757662, in order to use back main stack for signal handling. The main reason is that otherwise it is completely pointless that we do a lot of efforts to print the stack trace on crash, and the content of the stack and registers as well. Using an alternate stack broken this feature completely.
-
由 antirez 提交于
Now it uses the new wait_for_condition testing primitive. Also wait_for_condition implementation was fixed in this commit to properly escape the expr command and its argument.
-
由 antirez 提交于
A new primitive wait_for_condition was introduced in the scripting engine that makes waiting for events simpler, so that it is simpler to write tests that are more resistant to timing issues.
-
由 David Tran 提交于
-
- 25 4月, 2012 13 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
1) One integer "immediate" encoding that can encode from 0 to 12 in the encoding byte itself. 2) One 8 bit signed integer encoding that can encode 8 bit signed small integers in a single byte. The idea is to exploit all the not used bits we have around in a backward compatible way.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Grisha Trubetskoy 提交于
fit in 24 bits (thanks to antirez for catching and solving the two's compliment bug). Increment REDIS_RDB_VERSION to 6
-
由 antirez 提交于
-
由 antirez 提交于
This fixes compilation on FreeBSD (and possibly other systems) by not using ucontext_t at all if HAVE_BACKTRACE is not defined. Also the ifdefs to get the registers are modified to explicitly test for the operating system in the first level, and the arch in the second level of nesting.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Michael Schlenker 提交于
Tcl's exec can send data to stdout itself, no need to call cat/echo for that usually.
-
- 22 4月, 2012 2 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
Two limits are added: 1) Up to SLOWLOG_ENTRY_MAX_ARGV arguments are logged. 2) Up to SLOWLOG_ENTRY_MAX_STRING bytes per argument are logged. 3) slowlog-max-len is set to 128 by default (was 1024). The number of remaining arguments / bytes is logged in the entry so that the user can understand better the nature of the logged command.
-
- 21 4月, 2012 2 次提交
- 20 4月, 2012 1 次提交
-
-
由 antirez 提交于
-