Tj Holowaychuk
d268e36a27
Added redis-cli interactive help support
...
updated via commands.json in redis-doc repo. Currently
use `make src/help.h` to re-generate. The following
are valid from the REPL:
help
help [command]
help [group]
help groups
ex:
help sort
help hash
2010-11-16 05:50:26 -08:00
antirez
f6b6fda9e4
merge conflict resolved
2010-10-28 22:59:47 +02:00
Pieter Noordhuis
142fedcf37
Rewrite comment that was no longer valid
2010-10-28 16:59:05 +01:00
Pieter Noordhuis
abba73b7c0
When REDIS_CLOSE_AFTER_REPLY is set, there may never be new replies
2010-10-28 16:52:23 +01:00
Pieter Noordhuis
72bd886c36
Unify two client flags that mean the same
2010-10-28 15:07:45 +01:00
antirez
7c64c6168b
Merge remote branch 'remotes/pietern/zrevrangebyscore'
2010-10-28 14:12:25 +02:00
antirez
93d2466d19
removed useless spaces from DEBUG OBJECT output
2010-10-27 17:11:17 +02:00
Pieter Noordhuis
be8c4af304
Return error to client on wrong type for HMGET
2010-10-26 12:33:17 +02:00
antirez
98dd9e1699
added a missing prototype from syncio.c in redis.h
2010-10-25 10:54:37 +02:00
antirez
64a61269df
more generally usable i/o functions moved to syncio.c
2010-10-25 10:53:28 +02:00
antirez
db874d3c9a
synchronous I/O networking functions originally used just for replication refactored in a file as generally useful, they are used in the cluster branch for MIGRATE.
2010-10-24 16:22:52 +02:00
Pieter Noordhuis
c2d7ac73e0
Exclusively use either tcmalloc or OSX's native malloc_size()
2010-10-23 10:18:48 +02:00
Pieter Noordhuis
4e16ffcbb2
Don't use prefix when malloc_size() can be called
...
Also, use tcmalloc functions explicitly via macros to prevent symbol
lookups to resolve to native malloc/free on OSX.
2010-10-23 09:59:28 +02:00
antirez
a16fba68d1
Make sure to reset the signal handler and deliver again the original crashing signal when dumping the stack trace. This will allow to dump the core if core dumping is enabled.
2010-10-22 23:30:48 +02:00
Robey Pointer
ea70b63528
if server.saveparamslen is not set, don't save the DB on exit.
2010-10-22 23:17:28 +02:00
antirez
49cf03e61e
README more specific about tcmalloc space benefits
2010-10-22 00:18:26 +02:00
antirez
072f559c69
Makefile typo fixed for tcmalloc option
2010-10-22 00:16:32 +02:00
antirez
88be537ec2
reports if tcmalloc is in used in INFO output
2010-10-22 00:10:17 +02:00
antirez
927cbe3c5d
support for compiling with tcmalloc
2010-10-22 00:06:44 +02:00
antirez
afdb946851
version bumped to 2.1.5
2010-10-21 17:55:44 +02:00
Pieter Noordhuis
3675200982
Skip object encoding where it doesn't make sense
2010-10-17 18:13:31 +02:00
Pieter Noordhuis
dd0a3b1633
Object encoding in hash function is done by a more specific function
2010-10-17 17:46:55 +02:00
Pieter Noordhuis
b9accd41ec
Removed unused command flags
2010-10-17 17:31:40 +02:00
Pieter Noordhuis
000b46faac
Convert objects in the command procs instead of the protocol code
2010-10-17 17:21:41 +02:00
Pieter Noordhuis
1b6e1467d5
Prevent clients from making too large multibulk requests
2010-10-15 19:15:38 +02:00
Pieter Noordhuis
01797ad67a
Add benchmark for MSET
2010-10-15 18:17:06 +02:00
antirez
624eb51b92
prevent small integer sharing when maxmemory is active. So every object will use a private LRU field and the LRU algorithm can work well
2010-10-15 18:04:05 +02:00
Pieter Noordhuis
ff50d2621e
Change protocol from bulk to inline in redis-benchmark
2010-10-15 17:34:20 +02:00
Pieter Noordhuis
c5a32adaed
Don't reset the client when processCommand returns REDIS_ERR
2010-10-15 17:27:05 +02:00
Pieter Noordhuis
9ddc6fded8
Change tests to use either the inline or the multibulk protocol
2010-10-15 17:25:20 +02:00
Pieter Noordhuis
4865ad620b
Show output of leaks command on a leak
2010-10-15 15:56:16 +02:00
Pieter Noordhuis
a2459dd4e7
Change tcl client to only use the multibulk protocol
2010-10-15 15:50:29 +02:00
Pieter Noordhuis
0448515c58
Refactor request parsing code for efficiency
2010-10-15 15:44:55 +02:00
Pieter Noordhuis
0d4eb0937e
Add tests for OK on QUIT
2010-10-15 12:54:53 +02:00
antirez
db2e9181be
CONFIG RESETSTAT no longer resets the server uptime. Now keyspace hits/misses are reset as well.
2010-10-15 12:29:05 +02:00
antirez
c69dbab8ac
minor aesthetic change
2010-10-15 12:22:48 +02:00
antirez
99fef368e7
added keyspace_hits and keyspace_misses fields in INFO output
2010-10-15 12:19:21 +02:00
antirez
dad521b88d
maxmemory-samples implemented in CONFIG command and configuration file
2010-10-15 11:57:38 +02:00
antirez
4022964d64
Don't increment dirty on expireIfNeeded() as natural expires are not considered database changes. This will avoid useless read-only commands in the AOF file as a result of, for instance, a GET operation triggering an expirIfNeeded() call resulting in an expired key removed.
2010-10-15 11:29:03 +02:00
antirez
a436312c2c
Merge remote branch 'pietern/ziplist-regression'
2010-10-14 21:23:01 +02:00
antirez
25967801ea
implemented different algorithms for maxmemory
2010-10-14 21:22:21 +02:00
Pieter Noordhuis
d53a991b11
Replace ziplist stresser and fix regression
2010-10-14 21:11:42 +02:00
antirez
4c1af00e16
Object approximated LRU algorithm enhanced / fixed / refactored. This is used for the VM currently but will soon be used for maxmemory expiring.
2010-10-14 13:52:58 +02:00
Pieter Noordhuis
4bd7afa4d2
Return error when min and/or max in the sorted set range spec is not a double
2010-10-13 21:59:24 +02:00
Pieter Noordhuis
ce0eab01d5
Make ZREMRANGEBYSCORE accept the same range spec as ZRANGEBYSCORE
...
This allows to use inclusive/exclusive bounds for min and max when
deleting a range of scores from a sorted set.
2010-10-13 21:43:58 +02:00
Pieter Noordhuis
b18811fd90
Merge branch 'master' into zrevrangebyscore
2010-10-13 20:29:50 +02:00
Pieter Noordhuis
f19ee10824
Return OK on QUIT
2010-10-13 11:25:40 +02:00
Pieter Noordhuis
c8f88af7ca
Allow to specify which specific test files to run
2010-10-13 09:26:44 +02:00
antirez
7a75522315
free memory if the maxmemory parameter is reduced via CONFIG SET
2010-10-11 16:46:21 +02:00
antirez
5b2e5ee87e
maxmemory fixed, we now try to release memory just before we check for the memory limit. Before fixing there was code between the attempt to free memory and the check for memory limits, and this code could result into allocations going again after the memory limit.
2010-10-11 13:05:09 +02:00