- 04 Oct, 2018 1 commit
-
-
antirez authored
-
- 02 Oct, 2018 7 commits
-
-
antirez authored
-
antirez authored
This is useful in order to spot bugs where we fail at updating the pointer returned by the insertion function. Normally often the same pointer is returned, making it harder than needed to spot bugs. Related to #5210.
-
antirez authored
-
antirez authored
Most of the times the pointer will remain the same since integers of similar size don't take more space in listpacks. Related to #5210.
-
Salvatore Sanfilippo authored
Streams: update listpack with new pointer in XDEL
-
Salvatore Sanfilippo authored
bugfix: replace lastcmd with cmd when rewrite BRPOPLPUSH as RPOPLPUSH
-
Salvatore Sanfilippo authored
script cache memory in INFO and MEMORY includes both script code and overheads
-
- 01 Oct, 2018 6 commits
-
-
Salvatore Sanfilippo authored
Fix invalid use of sdsZmallocSize on an embedded string
-
Salvatore Sanfilippo authored
Fix incorrect memory usage accounting in zrealloc
-
Salvatore Sanfilippo authored
fix #5024 - commandstats for multi-exec were logged as EXEC.
-
Salvatore Sanfilippo authored
fix dict get on not found
-
Hamid Alaei authored
-
antirez authored
-
- 30 Sep, 2018 3 commits
-
-
Bruce Merry authored
When HAVE_MALLOC_SIZE is false, each call to zrealloc causes used_memory to increase by PREFIX_SIZE more than it should, due to mis-matched accounting between the original zmalloc (which includes PREFIX size in its increment) and zrealloc (which misses it from its decrement). I've also supplied a command-line test to easily demonstrate the problem. It's not wired into the test framework, because I don't know TCL so I'm not sure how to automate it.
-
Bruce Merry authored
sdsZmallocSize assumes a dynamically allocated SDS. When given a string object created by createEmbeddedStringObject, it calls zmalloc_size on a pointer that isn't the one returned by zmalloc
-
- 28 Sep, 2018 2 commits
-
-
antirez authored
See issue #5394.
-
zhaozhao.zz authored
There are two problems if we use lastcmd: 1. BRPOPLPUSH cannot be rewrited as RPOPLPUSH in multi/exec In mulit/exec context, the lastcmd is exec. 2. Redis will crash when execute RPOPLPUSH loading from AOF In fakeClient, the lastcmd is NULL.
-
- 27 Sep, 2018 5 commits
- 26 Sep, 2018 5 commits
- 25 Sep, 2018 7 commits
-
-
Salvatore Sanfilippo authored
add missing argument to function doc
-
Salvatore Sanfilippo authored
Fix typo in comment
-
antirez authored
-
antirez authored
-
antirez authored
Storing the context is useless, because we can't really reuse that later. For instance in the API RM_DictNext() that returns a RedisModuleString for the next key iterated, the user should pass the new context, because we may run the keys of the dictionary in a different context of the one where the dictionary was created. Also the dictionary may be created without a context, but we may still demand automatic memory management for the returned strings while iterating.
-
antirez authored
-
antirez authored
By using the "C" suffix for functions getting pointer/len, we can do the same in the future for other modules APIs that need a variant with pointer/len and that are now accepting a RedisModuleString.
-
- 24 Sep, 2018 4 commits
-
-
antirez authored
The burden of having to always create RedisModuleString objects within a module context was too much, especially now that we have threaded operations and modules are doing more interesting things. The context in the string API is currently only used for automatic memory managemnet, so now the API was modified so that the user can opt-out this feature by passing a NULL context.
-
antirez authored
-
Pavel Skuratovich authored
-
antirez authored
-