- 17 Oct, 2018 5 commits
-
-
antirez authored
-
antirez authored
Related to #5426.
-
antirez authored
Keep vanilla stream commands at toplevel, see #5426.
-
zhaozhao.zz authored
-
zhaozhao.zz authored
XSTREAM CREATE <key> <id or *> -- Create a new empty stream. XSTREAM SETID <key> <id or $> -- Set the current stream ID.
-
- 15 Oct, 2018 8 commits
-
-
antirez authored
Related to #5437.
-
antirez authored
Avoid storing the dirty value. See #5437.
-
antirez authored
See #5437 but also I updated a previous usage of the same var name.
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
Because the NACK->consumer is NULL, if idletime < minidle the NACK does not belong to any consumer, then redis will crash in XPENDING.
-
zhaozhao.zz authored
-
antirez authored
Issue #5433.
-
- 09 Oct, 2018 6 commits
-
-
antirez authored
See #5141.
-
zhaozhao.zz authored
Slaves and rebooting redis may have different radix tree struct, by different stream* config options. So propagating approximated MAXLEN to AOF/slaves may lead to date inconsistency.
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
If we rewrite the MAXLEN argument as zero when no trimming was performed, date between master and slave and aof will be inconsistent, because `xtrim maxlen 0` means delete all entries in stream.
-
antirez authored
-
- 03 Oct, 2018 5 commits
-
-
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.
-
zhaozhao.zz authored
-
antirez authored
-
Guy Korland authored
-
- 29 Aug, 2018 3 commits
-
-
Sascha Roland authored
The conclusion, that a xread request can be answered syncronously in case that the stream's last_id is larger than the passed last-received-id parameter, assumes, that there must be entries present, which could be returned immediately. This assumption fails for empty streams that actually contained some entries which got removed by xdel, ... . As result, the client is answered synchronously with an empty result, instead of blocking for new entries to arrive. An additional check for a non-empty stream is required.
-
dejun.xdj authored
-
shenlongxing authored
-
- 02 Aug, 2018 3 commits
- 30 Jul, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 24 Jul, 2018 2 commits
-
-
antirez authored
After #5161 the code could be made a bit more obvious for newcomers.
-
zhaozhao.zz authored
-
- 23 Jul, 2018 1 commit
-
-
antirez authored
For some reason I made a merge fiasco between 5.0 and unstable. This fixes the error introduced by merging unstable.
-
- 17 Jul, 2018 3 commits
- 16 Jul, 2018 3 commits
-
-
zhaozhao.zz authored
-
antirez authored
-
antirez authored
Related to #5129.
-