|
Revision tags: 8.0-m02, 6.2.16, 7.2.6, 7.4.1, 8.0-m01, 7.4.0, 7.4-rc2, 7.4-rc1, 7.2.5, 7.2.4, 7.0.15, 7.2.3, 7.2.2, 7.0.14, 6.2.14, 6.2.15, 7.2.1, 7.0.13, 7.2.0, 7.2-rc3, 7.0.12, 6.2.13, 6.0.20, 7.2-rc2, 6.0.19, 6.2.12, 7.0.11, 7.2-rc1, 7.0.10, 7.0.9, 6.2.11, 6.0.18, 6.2.10, 6.0.17, 6.2.9, 7.0.8, 7.0.7, 7.0.6, 6.2.8, 7.0.5, 7.0.4, 7.0.3, 7.0.2, 7.0.1, 7.0.0, 6.2.7, 7.0-rc3, 7.0-rc2, 7.0-rc1, 6.2.6, 6.0.16, 5.0.14, 5.0.13, 6.0.15, 6.2.5, 6.0.14, 6.2.4, 6.2.3, 6.0.13, 6.2.2, 6.2.1, 6.0.12, 5.0.12, 6.0.11, 6.2.0, 5.0.11, 6.2-rc3, 6.0.10, 6.2-rc2, 6.2-rc1, 6.0.9, 5.0.10, 6.0.8, 6.0.7, 6.0.6, 6.0.5, 6.0.4, 6.0.3, 6.0.2, 6.0.1, 6.0.0, 5.0.9, 6.0-rc4, 6.0-rc3, 5.0.8, 6.0-rc2, 6.0-rc1, 5.0.7, 5.0.6, 5.0.5, 3.2.13, 4.0.14, 5.0.4, 4.0.13, 5.0.3, 4.0.12, 5.0.2, 5.0.1, 5.0.0, 5.0-rc6, 5.0-rc5, 4.0.11, 5.0-rc4, 5.0-rc3, 5.0-rc2, 4.0.10, 3.2.12, 5.0-rc1, 4.0.9, 4.0.8, 4.0.7, 4.0.6, 4.0.5, 4.0.4, 4.0.3, 3.2.11, 4.0.2, 3.2.10, 4.0.1, 4.0.0, 3.2.9, 4.0-rc3, 3.2.8, 3.2.7, 3.2.6, 4.0-rc2, 4.0-rc1, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0, 3.2.0-rc3, 3.0.7, 3.2.0-rc2, 3.2-rc1, 3.0.6, 2.8.24, 3.0.5, 2.8.23, 2.8.22, 3.0.4 |
|
| #
32f80e2f |
| 27-Jul-2015 |
antirez <[email protected]> |
RDMF: More consistent define names.
|
| #
2d9e3eb1 |
| 26-Jul-2015 |
antirez <[email protected]> |
RDMF: redisAssert -> serverAssert.
|
| #
554bd0e7 |
| 26-Jul-2015 |
antirez <[email protected]> |
RDMF: use client instead of redisClient, like Disque.
|
| #
cef054e8 |
| 26-Jul-2015 |
antirez <[email protected]> |
RDMF (Redis/Disque merge friendlyness) refactoring WIP 1.
|
|
Revision tags: 3.0.3, 3.0.2, 2.8.21, 2.8.20, 3.0.1, 3.0.0, 3.0.0-rc6, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 2.8.19, 2.8.18, 3.0.0-rc1, 2.8.17, 2.8.16, 2.8.15, 2.8.14 |
|
| #
25791550 |
| 01-Aug-2014 |
Matt Stancliff <[email protected]> |
pubsub: Return integers for NUMSUB, not strings
Also adds test for numsub — due to tcl being tcl, it doesn't capture the "numberness" of the fix, but now we at least have one test case for numsub.
pubsub: Return integers for NUMSUB, not strings
Also adds test for numsub — due to tcl being tcl, it doesn't capture the "numberness" of the fix, but now we at least have one test case for numsub.
Closes #1561
show more ...
|
|
Revision tags: 3.0.0-beta8 |
|
| #
59cf0824 |
| 16-Jul-2014 |
antirez <[email protected]> |
PubSub clients refactoring and new PUBSUB flag.
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 channel
PubSub clients refactoring and new PUBSUB flag.
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.
show more ...
|
|
Revision tags: 2.8.13, 3.0.0-beta7, 2.8.12, 2.8.11, 3.0.0-beta6, 2.8.10, 3.0.0-beta5, 3.0.0-beta4, 3.0.0-beta3, 2.8.9, 2.8.8 |
|
| #
82b53c65 |
| 20-Mar-2014 |
antirez <[email protected]> |
struct dictEntry -> dictEntry.
|
|
Revision tags: 3.0.0-beta2, 2.8.7, 2.8.6, 3.0.0-beta1 |
|
| #
344a065d |
| 10-Feb-2014 |
antirez <[email protected]> |
Cluster: don't propagate PUBLISH two times.
PUBLISH both published messages via Cluster bus and replication when cluster was enabled, resulting in duplicated message in the slave.
|
|
Revision tags: 2.8.5, 2.8.4, 2.6.17, 2.8.3, 2.8.2, 2.8.1, 2.8.0, 2.8.0-rc6, 2.8.0-rc5, 2.8.0-rc4, 2.6.16, 2.6.15, 2.8.0-rc3, 2.8.0-rc2, 2.8.0-rc1, 2.6.14-2, 2.6.14-1 |
|
| #
515a26bb |
| 21-Jun-2013 |
antirez <[email protected]> |
New API to force propagation.
The old REDIS_CMD_FORCE_REPLICATION flag was removed from the implementation of Redis, now there is a new API to force specific executions of a command to be propagated
New API to force propagation.
The old REDIS_CMD_FORCE_REPLICATION flag was removed from the implementation of Redis, now there is a new API to force specific executions of a command to be propagated to AOF / Replication link:
void forceCommandPropagation(int flags);
The new API is also compatible with Lua scripting, so a script that will execute commands that are forced to be propagated, will also be propagated itself accordingly even if no change to data is operated.
As a side effect, this new design fixes the issue with scripts not able to propagate PUBLISH to slaves (issue #873).
show more ...
|
| #
519c9e11 |
| 20-Jun-2013 |
antirez <[email protected]> |
Allow PUBSUB NUMSUB without channels.
The result is an empty list but it is handy to call it programmatically.
|
| #
455563fa |
| 20-Jun-2013 |
antirez <[email protected]> |
PUBSUB command implemented.
Currently it implements three subcommands:
PUBSUB CHANNELS [<pattern>] List channels with non-zero subscribers. PUBSUB NUMSUB [channel_1 ...] List number of subscrib
PUBSUB command implemented.
Currently it implements three subcommands:
PUBSUB CHANNELS [<pattern>] List channels with non-zero subscribers. PUBSUB NUMSUB [channel_1 ...] List number of subscribers for channels. PUBSUB NUMPAT Return number of subscribed patterns.
show more ...
|
|
Revision tags: 2.6.14, 2.6.13, 2.6.12, 2.6.10-3, 2.6.10-2, 2.6.11 |
|
| #
042ed270 |
| 04-Mar-2013 |
Gengliang Wang <[email protected]> |
Removed useless "return" statements in pubsub.c
(original commit message edited)
|
|
Revision tags: 2.6.10-1, 2.6.10, 2.6.9-1 |
|
| #
2039f1a3 |
| 21-Jan-2013 |
antirez <[email protected]> |
UNSUBSCRIBE and PUNSUBSCRIBE: always provide a reply.
UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe the client respectively all the channels and patters if called without ar
UNSUBSCRIBE and PUNSUBSCRIBE: always provide a reply.
UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe the client respectively all the channels and patters if called without arguments.
However when these functions are called without arguments, but there are no channels or patters we are subscribed to, the old behavior was to don't reply at all.
This behavior is broken, as every command should always reply. Also it is possible that we are no longer subscribed to a channels but we are subscribed to patters or the other way around, and the client should be notified with the correct number of subscriptions.
Also it is not pretty that sometimes we did not receive a reply at all in a redis-cli session from these commands, blocking redis-cli trying to read the reply.
This fixes issue #714.
show more ...
|
|
Revision tags: 2.6.9 |
|
| #
9d09ce39 |
| 16-Jan-2013 |
guiquanz <[email protected]> |
Fixed many typos.
|
|
Revision tags: 2.6.8-1, 2.6.8, 2.6.7-1, 2.6.7, 2.6.6, 2.4.18, 2.6.5, 2.6.4 |
|
| #
4365e5b2 |
| 08-Nov-2012 |
antirez <[email protected]> |
BSD license added to every C source and header file.
|
|
Revision tags: 2.6.3, 2.6.2, 2.6.1, 2.6.0, 2.6.0-rc8, 2.6.0-rc7, 2.4.17, 2.6.0-rc6, 2.4.16, 2.4.15, 2.6.0-rc5, 2.6.0-rc4, 2.4.14, 2.6.0-rc3, 2.6.0-rc2, 2.4.13, 2.4.12, 2.6.0-rc1, 2.4.11, 2.4.10, 2.4.9, 2.4.8 |
|
| #
355f8591 |
| 04-Feb-2012 |
antirez <[email protected]> |
Use less memory when emitting the protocol, by using more shared objects for commonly emitted parts of the protocol.
|
|
Revision tags: 2.4.7, 2.4.6, 2.4.5, 2.4.4, 2.4.3 |
|
| #
c0ba9ebe |
| 08-Nov-2011 |
antirez <[email protected]> |
dict.c API names modified to be more coincise and consistent.
|
|
Revision tags: 2.4.2, 2.2.15, 2.4.1, 2.4.0 |
|
| #
c563ce46 |
| 07-Oct-2011 |
antirez <[email protected]> |
propagate PUBLISH messages using the redis cluster nodes bus. Still need to process the incoming packets of that type. Work in progress.
|
| #
eab0e26e |
| 04-Oct-2011 |
antirez <[email protected]> |
replaced redisAssert() with redisAssertWithInfo() in a shitload of places.
|
|
Revision tags: 2.2.14, 2.4.0-rc8, 2.2.13, 2.4.0-rc7, 2.4.0-rc6, 2.4.0-rc5, 2.4.0-rc4, 2.2.12, 2.4.0-rc3, with-deprecated-diskstore, 2.2.111-scripting, 2.2.11, 2.2.110-scripting, 2.2.10, 2.2.9, 2.4.0-rc2, 2.4.0-rc1 |
|
| #
efc34087 |
| 25-May-2011 |
antirez <[email protected]> |
Fix for Pub/Sub system, introduced in Redis 2.2.6 with the new copy-on-write safe iterator semantics. In the hope this is the last bug I introduced this way.
|
|
Revision tags: 2.2.8, 2.2.107-scripting, 2.2.7, 2.2.106-scripting, 2.2.6, 2.2.105-scripting, 2.2.5, 2.2.4, 2.2.3, 3.0-alpha0, 2.0.5, 2.2.2, 2.2.1, 2.2.0, 2.2.0-rc4, 2.2.0-rc3, 2.3-alpha0, 2.2.0-rc2, 2.2.0-rc1, 2.2-alpha6, 2.2-alpha5, 2.0.4, v2.0.4-stable, 2.2-alpha4, 2.2-alpha3 |
|
| #
a375b077 |
| 17-Oct-2010 |
Pieter Noordhuis <[email protected]> |
Skip object encoding where it doesn't make sense
|
| #
75b41de8 |
| 17-Oct-2010 |
Pieter Noordhuis <[email protected]> |
Convert objects in the command procs instead of the protocol code
|
|
Revision tags: 2.0.3, v2.0.3-stable, 2.0.2, v2.0.2-stable, 2.0.1, v2.0.1-stable, 2.2-alpha2, 2.0.0, v2.0.0-stable, 2.2-alpha1, twitter-20100825, twitter-20100804, 2.2-alpha0, v2.0.0-rc4, v2.0.0-rc3, v2.0.0-rc2 |
|
| #
0f49d6b0 |
| 01-Jul-2010 |
antirez <[email protected]> |
minor aesthetic change
|
| #
e2641e09 |
| 21-Jun-2010 |
antirez <[email protected]> |
redis.c split into many different C files.
networking related stuff moved into networking.c
moved more code
more work on layout of source code
SDS instantaneuos memory saving. By Pieter and Salva
redis.c split into many different C files.
networking related stuff moved into networking.c
moved more code
more work on layout of source code
SDS instantaneuos memory saving. By Pieter and Salvatore at VMware ;)
cleanly compiling again after the first split, now splitting it in more C files
moving more things around... work in progress
split replication code
splitting more
Sets split
Hash split
replication split
even more splitting
more splitting
minor change
show more ...
|