- 02 9月, 2011 1 次提交
-
-
由 Konstantin Tokarev 提交于
Applied patch from Issue 119 provided by pahowes@gmail.com
-
- 09 8月, 2011 1 次提交
-
-
由 antirez 提交于
Auto rewrite integer overflow fixed. Thanks to Gaurav for finding it (see issue 602 on google code), and Pieter Noordhuis for tracing it.
-
- 22 7月, 2011 2 次提交
- 13 7月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 08 7月, 2011 1 次提交
-
-
由 antirez 提交于
Take a pointer to the relevant entry of the command table in the client structure. This is generally a more sounding design, simplifies a few functions prototype, and as a side effect fixes a bug related to the conversion of EXPIRE -1 to DEL: before of this fix Redis tried to convert it into an EXPIREAT in the AOF code, regardless of our rewrite of the command.
-
- 02 7月, 2011 2 次提交
- 30 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 25 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 20 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 17 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 12 6月, 2011 1 次提交
-
-
由 Hampus Wessman 提交于
Slight adjustment in growth calculation.
-
- 10 6月, 2011 7 次提交
- 01 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 31 5月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 29 5月, 2011 1 次提交
-
-
由 antirez 提交于
INFO now contains the time (in usecs) needed to fork() in order to persist. The info is available in the stats section of INFO.
-
- 25 5月, 2011 5 次提交
- 22 5月, 2011 1 次提交
-
-
由 Pieter Noordhuis 提交于
-
- 05 5月, 2011 2 次提交
-
-
由 Pieter Noordhuis 提交于
-
由 antirez 提交于
-
- 21 4月, 2011 3 次提交
-
-
由 antirez 提交于
peak fragmentation ratio removed as it is a confusing field for users and trivial to compute at hand now that there is peak memory information in INFO output
-
由 antirez 提交于
-
由 antirez 提交于
save peak memory usage as statistic and show it in INFO. Also a new INFO field was added showing the fragmentation ratio using the peak memory info.
-
- 19 4月, 2011 2 次提交
- 16 4月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 15 4月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 13 4月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 11 4月, 2011 1 次提交
-
-
由 Salvatore Sanfilippo 提交于
added minimal cluster section in INFO output. This is only useful to check if the instance is or not configured as a cluster node, all the other informations are accessible using the CLUSTER command.
-