- 10 Oct, 2014 1 commit
-
-
antirez authored
-
- 08 Oct, 2014 1 commit
-
-
antirez authored
We need to remember what is the saving strategy of the current RDB child process, since the configuration may be modified at runtime via CONFIG SET and still we'll need to understand, when the child exists, what to do and for what goal the process was initiated: to create an RDB file on disk or to write stuff directly to slave's sockets.
-
- 07 Oct, 2014 3 commits
- 06 Oct, 2014 2 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
ALL comment fixes
-
- 03 Oct, 2014 2 commits
-
-
antirez authored
-
antirez authored
However we don't try to do this if the integer is already inside a range representable with a shared integer. The performance gain appears to be around ~15% in micro benchmarks, however in the long run this also helps to improve locality, so should have more, hard to measure, benefits.
-
- 29 Sep, 2014 29 commits
-
-
Miguel Parramon authored
😄 Closes #2034 -
Ezequiel Lovelle authored
Closes #2029
-
Aniruddh Chaturvedi authored
Closes #2005
-
Gregory Petrosyan authored
Closes #2002
-
Matt Stancliff authored
-
Juarez Bochi authored
Closes #1960
-
T.J. Schuck authored
Closes #1938
-
Matt Stancliff authored
Some language in the comment was difficult to understand, so this commit: clarifies wording, removes unnecessary words, and relocates some dependent clauses closer to what they actually describe. I also tried to break up longer chains of thought (if X, then Y, and Q, and also F, so obviously M) into more manageable chunks for ease of understanding.
-
Xiaojie Zhang authored
Closes #1523
-
Jan-Erik Rediger authored
Closes #1739
-
Matt Stancliff authored
-
Matt Stancliff authored
-
Matt Stancliff authored
-
Matt Stancliff authored
- Remove trailing newlines from redis.conf - Fix comment misspelling - Clarifies zipEncodeLength usage and a C API mention (#1243, #1242) - Fix cluster typos (inspired by @papanikge #1507) - Fix rewite -> rewrite in a few places (inspired by #682) Closes #1243, #1242, #1507
-
Michael Parker authored
Closes #1351
-
Ted Nyman authored
Closes #1373
-
xuxiang authored
Closes #1386
-
Ben authored
Closes #1441
-
Aaron Rutkovsky authored
Closes #1513
-
Jan-Erik Rediger authored
Closes #1537
-
Agis Anastasopoulos authored
Closes #1544
-
Dmitry Chestnykh authored
Closes #1673
-
Juarez Bochi authored
Closes #1682
-
Jan-Erik Rediger authored
Closes #1713
-
zionwu authored
error != success; and 0 != number of bytes written Closes #1806
-
Jan-Erik Rediger authored
Closes #1871
-
Matt Stancliff authored
The core linenoise code was being backported, but not the README or example. It's less confusing for users if everything matches across directories. Fix inspired by @thrig Closes #1872
-
Lynn authored
Closes #1877
-
Manuel Meurer authored
Closes #1897
-
- 26 Sep, 2014 1 commit
-
-
antirez authored
-
- 25 Sep, 2014 1 commit
-
-
antirez authored
The old DEBUG POPULATE form for automatic creation of test keys is: DEBUG POPULATE <count> Now an additional form is available: DEBUG POPULATE <count> <prefix> When prefix is not specified, it defaults to "key", so the keys are named incrementally from key:0 to key:<count-1>. Otherwise the specified prefix is used instead of "key". The command is useful in order to populate different Redis instances with key names guaranteed to don't collide. There are other debugging uses, for example it is possible to add additional N keys using a count of N and a random prefix at every call.
-