- 02 4月, 2012 1 次提交
-
-
由 Premysl Hruby 提交于
-
- 01 4月, 2012 2 次提交
-
-
由 Salvatore Sanfilippo 提交于
chkconfig in install_server.sh doesn't work because of a typo
-
由 ThePicard 提交于
-
- 31 3月, 2012 3 次提交
- 30 3月, 2012 3 次提交
-
-
由 antirez 提交于
-
由 Joseph Jang 提交于
occurs when two or more dbs are replicated and at least one of them is >db10
-
由 antirez 提交于
-
- 29 3月, 2012 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
Fix for slaves chains. Force resync of slaves (simply disconnecting them) when SLAVEOF turns a master into a slave.
-
由 antirez 提交于
-
由 Nathan Fritz 提交于
(The original implementation was modified by @antirez to conform Redis coding standards.)
-
- 28 3月, 2012 8 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Redis test: regexp to check if valgrind reported errors modified. Now we no longer look at the total count because this includes "possibly lost" bytes that are not interesting for Redis (tons of false positives because of how sds.c works).
-
由 Salvatore Sanfilippo 提交于
fix typo
-
由 Salvatore Sanfilippo 提交于
Fixes around time usage
-
由 Premysl Hruby 提交于
-
由 Premysl Hruby 提交于
-
- 27 3月, 2012 8 次提交
-
-
由 Premysl Hruby 提交于
-
由 Premysl Hruby 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Produce the watchlog warning log in a way that is safer from a signal handler. Fix a memory leak in the backtrace generation function.
-
由 antirez 提交于
This is required to ensure that the signal will be delivered to the main thread when the watchdog timer expires.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
SIGSEGV handler refactored so that we can reuse stack trace and current client logging functionalities in other contexts.
-
- 25 3月, 2012 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
This new field counts all the times Redis is configured with AOF enabled and fsync policy 'everysec', but the previous fsync performed by the background thread was not able to complete within two seconds, forcing Redis to perform a write against the AOF file while the fsync is still in progress (likely a blocking operation).
-
由 antirez 提交于
Apparently because the sample RDB file was not copied before every test Redis had a chance to replace it with a newly written one, so that the next test could fail.
-
- 24 3月, 2012 7 次提交
- 23 3月, 2012 1 次提交
-
-
由 antirez 提交于
-