- 28 Oct, 2019 13 commits
-
-
Guy Benoish authored
Also, add an API for getting server.notify_keyspace_events Other (unrelated) changes: Add RM_GetKeynameFromModuleKey
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
Make module tests pass with valgrind, and fix a leak in diskless load
-
Salvatore Sanfilippo authored
Modules: improve tests Makefile.
-
Salvatore Sanfilippo authored
Module API for LatencyAddSample
-
Salvatore Sanfilippo authored
Fix some minor typos in comments
-
Salvatore Sanfilippo authored
fix comment typo in redis-cli.c
-
Salvatore Sanfilippo authored
Typo fix: kill -> still
-
Salvatore Sanfilippo authored
Introduce ReplyWithVerbatimString, ReplyWithEmptyArray, ReplyWithNull…
-
Salvatore Sanfilippo authored
Modules: make unloading module more safe
-
swilly22 authored
Introduce ReplyWithVerbatimString, ReplyWithEmptyArray, ReplyWithNullArray and ReplyWithEmptyString to redis module API
-
zhaozhao.zz authored
As we know if a module exports module-side data types, unload it is not allowed. This rule is the same with blocked clients in module, because we use background threads to implement module blocked clients, and it's not safe to unload a module if there are background threads running. So it's necessary to check if any blocked clients running in this module when unload it. Moreover, after that we can ensure that if no modules, then no module blocked clients even module unloaded. So, we can call moduleHandleBlockedClients only when we have installed modules.
-
- 25 Oct, 2019 3 commits
-
-
Carsten Strotmann authored
-
happynote3966 authored
-
Wander Hillen authored
-
- 24 Oct, 2019 6 commits
- 23 Oct, 2019 18 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
We can't use the same client at the same time when re-entering the hook.
-
antirez authored
-
antirez authored
Calling a module hook callback may result in callback operations in turn triggering other events the module is subscribed too. We don't want to trigger those, it's unsafe and quite confusing, and to do it correcly we would need to maintain an event list: quite a more complex implementation.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-