1614 Commits

Author SHA1 Message Date
antirez
9261880e78 conflict resolved in cherry pick 2011-02-22 00:03:03 +01:00
antirez
226157c42c suppress a Linux warning, for 2.2 sake 2011-02-21 17:51:52 +01:00
antirez
d6195c4344 check return value of getcwd() 2011-02-21 17:51:28 +01:00
antirez
8b011f5400 CONFIG SET/GET for all the special encoding parameters of sets, lists, hashes 2011-02-17 12:20:59 +01:00
antirez
efaf6a9be0 SPOP replication/AOF patch ported to unstable branch 2011-02-16 12:41:40 +01:00
antirez
fbfc62f406 CONFIG GET/SET dir implemented 2011-02-14 02:51:27 +01:00
antirez
fd16bf40d9 fixed two diskstore issues, a quasi-deadlock creating problems with I/O speed and a race condition among threads 2011-02-11 11:16:15 +01:00
antirez
eb9dfd27aa introduced a new logging function for big messages 2011-02-09 10:10:35 +01:00
antirez
552bc42754 Merge remote branch 'pietern/unstable-brpoplpush' into unstable 2011-02-07 15:28:01 +01:00
antirez
ae3212959f Fix for the previous port 0 patch, thanks to Pieter for noticing the error 2011-02-07 13:43:29 +01:00
antirez
16754f14e1 If port zero is specified, Redis will not listen for TCP connections 2011-02-07 12:52:01 +01:00
Pieter Noordhuis
a282e91b0f Clarify comment 2011-02-03 12:56:53 +01:00
Pieter Noordhuis
f9120df538 Reply with single null bulk for unsuccesful BRPOPLPUSH 2011-02-03 12:56:50 +01:00
antirez
317f61ad26 propagate key eviction to slaves and AOF, like for expires, so that replicas and AOFs are always consistent even in maxmemory mode. 2011-01-27 16:52:37 +01:00
antirez
17c4da8d7f Fixed a theoretical non exploitable security bug reported by @chrisrohlf. In theory if we undefine SDS_ABORT_ON_OOM from sds.c AND modify zmalloc.c in order to don't quit on out of memory (but this would break every other part of Redis), on out of memory there is a possible heap overflow. 2011-01-27 10:27:25 +01:00
antirez
dd3b5bfe69 TODO list updated 2011-01-26 10:42:32 +01:00
antirez
d136157383 INFO commandstats section reset with config resetstat, a new microseconds per call field, and a few other minor things 2011-01-24 10:56:06 +01:00
antirez
37631f2a3f portability fix in redis benchmark, using zu format specified with size_t instead of lu 2011-01-24 10:05:42 +01:00
antirez
9064ae9eac Now INFO outputs the "INFO default" output if no argument is passed. Also added counts of calls for every command, thanks to an idea by Mike Shaver 2011-01-23 22:14:15 +01:00
antirez
4187b3ef2a INFO output refactoring. Now "INFO section" will report only the specified section 2011-01-23 16:41:07 +01:00
antirez
daf98fde2f profiling information in INFO 2011-01-23 11:46:34 +01:00
antirez
3f3b6a3c6f Fixed issue #435 and at the same time introduced explicit ping in the master-slave channel that will detect a blocked master or a broken even if apparently connected TCP link. 2011-01-20 13:18:23 +01:00
antirez
4fe6e48723 Merge branch 'unstable' of github.com:antirez/redis into unstable 2011-01-20 11:00:25 +01:00
antirez
036aca44e2 Fixed compilation on FreeBSD 2011-01-20 10:59:49 +01:00
antirez
86de0078d4 a better release note for Redis unstable provided 2011-01-17 12:36:37 +01:00
Pieter Noordhuis
418603038c Remove client from list of unblocked clients when it is free'd 2011-01-17 10:04:13 +01:00
antirez
0c11bb668f default hash encoding settings also fixed in redis.conf 2011-01-15 22:31:07 +01:00
antirez
489ccb00d1 lame typo causing bad hashes memory characteristic 2011-01-15 22:24:22 +01:00
antirez
5286447c24 implemented two new INFO fields showing the size of clients max input and output buffers. 2011-01-14 10:20:02 +01:00
antirez
3e7c76253e master-slave replication fixed, it was not listing any key using KEYS command in the slave. 2011-01-14 09:53:57 +01:00
antirez
80a55ea680 redisServer structure fields reordered for clarity 2011-01-14 00:19:19 +01:00
antirez
9ef223a269 TODO modified 2011-01-10 21:45:08 +01:00
antirez
0606f2d3b1 minor aesthetic change in test suite messages 2011-01-09 22:17:08 +01:00
antirez
5cbd8e400f run both inmemory and diskstore tests. 2011-01-09 19:42:56 +01:00
antirez
d3aa7312b9 fixed bgsave_in_progress in INFO when BGSAVEing with diskstore enabled, don't DEBUG FLUSHCACHE when bgsave is in progress. 2011-01-09 19:25:34 +01:00
antirez
819b03213f DEBUG FLUSHCACHE needs to wait that everything was synched on disk 2011-01-09 19:01:44 +01:00
antirez
f261a5d500 test adapted to run with diskstore, and a few bugs fixed 2011-01-09 18:25:34 +01:00
antirez
ee853db29d initial fix of the test suite to run both in in-memory and diskstore mode 2011-01-09 16:49:52 +01:00
antirez
e3401df98d allocation stats in INFO 2011-01-09 15:56:50 +01:00
antirez
284ff96881 TODO updated 2011-01-08 02:07:48 +01:00
antirez
2e31c54134 DEBUG OBJECT fixed with diskstore, force loading 2011-01-08 02:06:01 +01:00
antirez
76ca46d020 resolved a problem with delayed loading of keys 2011-01-08 01:42:08 +01:00
antirez
c378cabde7 blocking SAVE implemented 2011-01-08 00:09:57 +01:00
antirez
73bfb15a9f avoid bgsaving temp files 2011-01-07 23:51:31 +01:00
antirez
d9b79fb3ef diskstore BGSAVE should work now 2011-01-07 23:41:00 +01:00
antirez
85fa300825 more work towards diskstore bgsave 2011-01-07 19:31:42 +01:00
antirez
e6fdae80f8 source reshaped a bit to play well with a bgsaving thread, still work to do, does not compile. 2011-01-07 18:15:14 +01:00
antirez
2a451f4363 Merge branch 'unstable' of github.com:antirez/redis-private into unstable 2011-01-07 16:43:51 +01:00
antirez
6e26d09dde TODO updated 2011-01-07 16:43:36 +01:00
antirez
9f986a15ff BGSAVE work in progress 2011-01-05 18:38:31 +01:00