- 27 8月, 2014 19 次提交
-
-
由 Joshua Anderson 提交于
Closes #1610
-
由 cubicdaiya 提交于
According to the C standard, it is desirable to give the type 'void' to functions have no argument. Closes #1631
-
由 Matt Stancliff 提交于
dictAdd returns DICT_OK, not REDIS_OK. They both have the same underlying values, so it works even though the code is technically wrong. Fixes #1512
-
由 Jan-Erik Rediger 提交于
This was discovered by _bodya and reported in the IRC channel. Everything worked fine as these scripts are always executed as shell scripts. Closes #1728
-
由 Edgars Irmejs 提交于
According to unix manuals, "Connecting to the socket object requires read/write permission." -- mode 755 is useless for anybody other than the owner. Fixes #1696
-
由 ripcurld00d 提交于
Use constants to avoid magic numbers in `types`, which is an array that stores the names of `REDIS` types. Closes #1681
-
由 Kashif Rasul 提交于
Modified by @antirez since the original fix to genInfoString() looked weak. Probably the clang analyzer complained about `section` being possibly NULL, and strcasecmp() called with a NULL pointer. In the practice this can never happen, still for the sake of correctness the right fix is not to modify only the first call, but to set `section` to the value of "default" if it happens to be NULL. Closes #1660
-
由 antirez 提交于
Also quit ASAP when we are still loading a DB, since care is not needed in this special condition, especially for a SIGINT.
-
由 Matt Stancliff 提交于
-
由 Matt Stancliff 提交于
The classic (min+max)/2 is provably unsafe. Fixed as recommended in research: http://googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html Fix inspired by @wjin, but I used a different approach. (later, I found @kuebler fixed the same issue too). Fixes #1741, #1602
-
由 Jan-Erik Rediger 提交于
Previously the end was casted to a smaller type which resulted in a wrong check and failed with values larger than handled by unsigned. Closes #1847, #1844
-
由 Matt Stancliff 提交于
Negative key count causes segfault in Lua functions. Fixes #1842 Closes #1843
-
由 Jan-Erik Rediger 提交于
(Cleaned up a little by @mattsta) Closes #1774
-
由 Wei Jin 提交于
Fixes #1741
-
由 antirez 提交于
-
由 siahl 提交于
Closes #1900
-
由 Matt Stancliff 提交于
Some people need formatted output even when they have no interactive tty. Fixes #760
-
由 Matt Stancliff 提交于
Previously redis-cli would happily show "-1" or "99999" as valid DB choices. Now, if the SELECT call returned an error, we don't update the DB number in the CLI. Inspired by @anupshendkar in #1313 Fixes #566, #1313
-
由 Matt Stancliff 提交于
Previously, if you did SELECT then AUTH, redis-cli would show your SELECT'd db even though it didn't happen. Note: running into this situation is a (hopefully) very limited used case of people using multiple DBs and AUTH all at the same time. Fixes antirez#1639
-
- 28 7月, 2014 3 次提交
-
-
由 Yossi Gottlieb 提交于
-
由 Salvatore Sanfilippo 提交于
* fixed doc URL for keyspace events
-
由 vps 提交于
-
- 25 7月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 24 7月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 23 7月, 2014 2 次提交
-
-
由 antirez 提交于
Based on ideas documented in this blog post: https://www.facebook.com/notes/facebook-engineering/three-optimization-tips-for-c/10151361643253920 The original code was modified to handle signed integers, reformetted to fit inside the Redis code base, and was stress-tested with a program in order to validate the implementation against snprintf(). Redis was measured to be measurably faster from the point of view of clients in real-world operations because of this change, since sometimes number to string conversion is used extensively (for example every time a GET results into an integer encoded object to be returned to the user).
-
由 antirez 提交于
This is just a quickfix, for the nature of the test the right way to fix it is to average the error of N runs, since otherwise it is always possible to get a false positive with a bad run, or to minimize too much this possibility we may end testing with too much "large" error ranges.
-
- 22 7月, 2014 4 次提交
-
-
由 antirez 提交于
This is not a regression but issue #1786 showed the need for this test.
-
由 antirez 提交于
-
由 antirez 提交于
The user @kjmph provided excellent ideas to improve speed of ZUNIONSTORE (in certain cases by many order of magnitude), together with an implementation of the ideas. While the ideas were sounding, the implementation could be improved both in terms of speed and clearness, so that's my attempt at reimplementing the speedup proposed, trying to improve by directly using just a dictionary with an embedded score inside, and reusing the single-pass aggregate + order-later approach. Note that you can't apply this commit without applying the previous commit in this branch that adds a double in the dictEntry value union. Issue #1786.
-
由 antirez 提交于
-
- 18 7月, 2014 6 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
In order to make sure every object has its own private LRU counter, when maxmemory is enabled tryObjectEncoding() does not use the pool of shared integers. However when the policy is not LRU-based, it does not make sense to do so, and it is much better to save memory using shared integers.
-
由 antirez 提交于
PING can now be called with an additional arugment, behaving exactly like the ECHO command. PING can now also be called in Pub/Sub mode (with one more more subscriptions to channels / patterns) in order to trigger the delivery of an asynchronous pong message with the optional payload. This fixes issue #420.
-
由 antirez 提交于
The code tested many times if a client had active Pub/Sub subscriptions by checking the length of a list and dictionary where the patterns and channels are stored. This was substituted with a client flag called REDIS_PUBSUB that is simpler to test for. Moreover in order to manage this flag some code was refactored. This commit is believed to have no effects in the behavior of the server.
-
- 14 7月, 2014 2 次提交
-
-
由 antirez 提交于
-
由 michael-grunder 提交于
Previously, the command definition for the OBJECT command specified a minimum of two args (and that it was variadic), which meant that if you sent this: OBJECT foo When cluster was enabled, it would result in an assertion/SEGFAULT when Redis was attempting to extract keys. It appears that OBJECT is not variadic, and only ever takes 3 args. https://gist.github.com/michael-grunder/25960ce1508396d0d36a
-
- 11 7月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 10 7月, 2014 1 次提交
-
-
由 antirez 提交于
-