08c3fe8063
- memcpy(&id,ri.key,ri.key_len);
...
+ memcpy(&id,ri.key,sizeof(id));
The memcpy from the key to the id reliease on the fact that this key
*should* be 8 bytes long as it was entered as such a few lines up the
code.
BUT if someone will change the code to the point this is no longer true,
current code can trash the stack which makes debugging very hard
while this fix will result in some garbage id, or even page fault.
Both are preferable to stack mangaling.
2019-12-05 13:37:11 +00:00
c98e7717bb
Client side caching: show tracking slots usage in INFO.
2019-07-23 11:02:14 +02:00
9268493e8d
Client side caching: implement full slot limit function.
2019-07-23 10:57:22 +02:00
9012e587ca
Client side caching: do not reclaim tracking table if it's empty
2019-07-23 15:25:00 +08:00
c41f94d2a3
Client side caching: split invalidation into key / slot.
2019-07-22 18:59:53 +02:00
7d3992a80a
Client side caching: reclaim the tracking table on FLUSHALL.
2019-07-22 12:33:49 +02:00
f850201c64
Client side caching: don't hash the key if not needed.
2019-07-22 12:10:51 +02:00
e00442eb13
Clinet side caching: take count of used caching slots.
2019-07-22 11:47:44 +02:00
f59119aad6
Client side caching: filter clients untracking
2019-07-18 16:46:19 +08:00
6191ea90a1
Client side caching: implement trackingInvalidateKeysOnFlush()
2019-07-17 20:33:52 +08:00
dad0e916ff
Client side caching: filter clients no longer there.
2019-07-10 19:46:46 +02:00
6b29f2d83d
Client side caching: RESP2 support.
2019-07-05 12:24:28 +02:00
3e43aed1ac
Client side caching: fix invalidate message len and content.
2019-07-04 14:07:23 +02:00
46edb55de9
Client side caching: implement trackingInvalidateKey().
2019-07-03 19:16:20 +02:00
