summaryrefslogtreecommitdiff
path: root/src/redis-cli.c
Commit message (Collapse)AuthorAgeFilesLines
* redis-cli: "allocator-stats" -> "malloc-stats".antirez2016-09-191-1/+1
| | | | | It was changed in Redis but not in redis-cli. Thanks to @oranagra for signaling.
* MEMORY DOCTOR initial implementation.antirez2016-09-161-1/+2
|
* Memory related subcommands of DEBUG moved to MEMORY.antirez2016-09-161-2/+3
|
* redis-cli LRU test mode: randomize value of key when setting.antirez2016-07-181-1/+4
| | | | | This way it is possible from an observer to tell when the key is replaced with a new one having the same name.
* redis-cli LRU test mode: remove newline from key names.antirez2016-07-181-1/+1
|
* redis-cli: check SELECT reply type just in state updated.antirez2016-07-051-1/+1
| | | | | | | | | | | | In issues #3361 / #3365 a problem was reported / fixed with redis-cli not updating correctly the current DB on error after SELECT. In theory this bug was fixed in 0042fb0e, but actually the commit only fixed the prompt updating, not the fact the state was set in a wrong way. This commit removes the check in the prompt update, now that hopefully it is the state that is correct, there is no longer need for this check.
* Fix for redis_cli printing default DB when select command fails.sskorgal2016-07-011-1/+1
|
* redis-cli: really connect to the right server.antirez2016-06-161-2/+5
| | | | | | | | | | | | | I recently introduced populating the autocomplete help array with the COMMAND command if available. However this was performed before parsing the arguments, defaulting to instance 6379. After the connection is performed it remains stable. The effect is that if there is an instance running on port 6339, whatever port you specify is ignored and 6379 is connected to instead. The right port will be selected only after a reconnection. Close #3314.
* Remove debug printingJan-Erik Rediger2016-05-211-3/+0
|
* redis-cli: integrate help.h with COMMAND output.antirez2016-05-071-10/+70
| | | | | | | Use the COMMAND output to fill with partial information the built-in help. This makes redis-cli able to at least complete commands that are exported by the Redis server it is connected to, but were not available in the help.h file when the redis-cli binary was compiled.
* redis-cli: remove debugging message.antirez2016-05-051-1/+0
|
* Merge pull request #3008 from badboy/fix-2911Salvatore Sanfilippo2016-05-051-1/+1
|\ | | | | Fix nanosecond conversion
| * Fix nanosecond conversionJan-Erik Rediger2016-01-131-1/+1
| | | | | | | | | | | | 1 microsecond = 1000 nanoseconds 1e3 = 1000 10e3 = 10000
* | redis-cli: don't free historyfile, is used later.antirez2016-05-051-1/+1
| |
* | Merge pull request #3077 from Palethorn/ipv6-redirect-parseSalvatore Sanfilippo2016-05-051-1/+1
|\ \ | | | | | | Fix for #3076 Reverse redirect address parse
| * | Reverse redirect address parseDavid Cavar2016-02-091-1/+1
| | | | | | | | | Fix issue in case the redirect address is in ipv6 format. Parse from behind to extract last part of the response which represents actual port.
* | | Minor redis-cli wording change in --help output.antirez2016-05-041-1/+2
| | |
* | | add DEBUG JEMALLC PURGE and JEMALLOC INFO cleanupOran Agra2016-04-251-1/+1
| | |
* | | redis-cli preferences and rc file support.antirez2016-04-131-17/+85
| | |
* | | redis-cli hints.antirez2016-04-131-0/+53
|/ /
* | Lua debugger: support direct calls to SCRIPT DEBUG in redis-cli.antirez2016-01-081-0/+21
|/ | | | | | | | | Previously it was possible to activate a debugging session only using the --ldb option in redis-cli. Now calling SCRIPT DEBUG can also activate the debugging mode without putting the redis-cli in a desynchronized state. Related to #2952.
* fix sprintf and snprintf format stringantirez2015-11-281-2/+2
| | | | | | | There are some cases of printing unsigned integer with %d conversion specificator and vice versa (signed integer with %u specificator). Patch by Sergey Polovko. Backported to Redis from Disque.
* Lua debugger: redis-cli: allow restart after end of session.antirez2015-11-171-1/+3
|
* Lua debugger: redis-cli can restart Lua debugging sessions.antirez2015-11-171-44/+74
|
* Lua debugger: maxlen command implemented.antirez2015-11-171-0/+1
| | | | Let the user control the replies truncation.
* Lua debugger: redis-cli: show compile errors in LDB mode.antirez2015-11-171-3/+12
|
* Lua debugger: redis-cli error when --ldb is without --eval.antirez2015-11-171-0/+7
| | | | | Otherwise the result is a messed CLI without prompt. Thanks to Itamar Haber for reporting this issue.
* Lua debugger: use sds_malloc() to allocate eval cli array.antirez2015-11-171-1/+1
| | | | | | | | | | | | | Redis-cli handles the debugger "eval" command in a special way since sdssplitargs() would not be ok: we need to send the Redis debugger the whole Lua script without any parsing. However in order to later free the argument vector inside redis-cli using just sdsfreesplitres(), we need to allocate the array of SDS pointers using the same allocator SDS is using, that may differ to what Redis is using. So now a newer version of SDS exports sds_malloc() and other allocator functions to give access, to the program it is linked to, the allocator used internally by SDS.
* Lua debugger: better support for synchronous mode.antirez2015-11-171-3/+16
|
* Lua debugger: inform user changes are rolled back.antirez2015-11-171-1/+1
| | | | | When redis-cli will support the synchronous mode, this will not be printed.
* Lua debugger: clear end of session protocol.antirez2015-11-171-9/+19
| | | | | | | When the debugger exits now it produces an <endsession> tag that informs redis-cli (or other debugging clients) that the session terminated. This way the client knows there is yet another reply to read (the one of the EVAL script itself), and can switch to non-debugging mode ASAP.
* Lua debugger: redis.debug() implemented.antirez2015-11-171-0/+1
|
* Lua debugger: redis-cli, mark end of debugging session.antirez2015-11-171-0/+1
|
* Lua debugger: much better Lua values pretty printer.antirez2015-11-171-1/+1
|
* Lua debugger: output improvements, eval command.antirez2015-11-171-6/+26
|
* Lua debugger: breakpoints.antirez2015-11-171-1/+53
|
* Lua debugger: log Redis commands. List command.antirez2015-11-171-0/+2
|
* Lua debugger: initial REPL.antirez2015-11-171-2/+10
|
* Lua debugger: foundations implemented.antirez2015-11-171-1/+18
|
* redis-cli pipe mode: don't stay in the write loop forever.antirez2015-09-301-1/+6
| | | | | | | | | | | | | The code was broken and resulted in redis-cli --pipe to, most of the times, writing everything received in the standard input to the Redis connection socket without ever reading back the replies, until all the content to write was written. This means that Redis had to accumulate all the output in the output buffers of the client, consuming a lot of memory. Fixed thanks to the original report of anomalies in the behavior provided by Twitter user @fsaintjacques.
* SCAN iter parsing changed from atoi to chartoullubuntu2015-09-071-1/+1
|
* RDMF: More consistent define names.antirez2015-07-271-2/+2
|
* sds size classes - memory optimizationOran Agra2015-07-141-2/+2
|
* DEBUG HTSTATS <dbid> added.antirez2015-07-141-3/+3
| | | | | | | | The command reports information about the hash table internal state representing the specified database ID. This can be used in order to investigate rehashings, memory usage issues and for other debugging purposes.
* redis-cli --latency-dist: one gray more, and --mono support.antirez2015-02-131-7/+17
|
* redis-cli --latency-dist, hopefully better palette.antirez2015-02-131-2/+2
| | | | | | | | | Less grays: more readable palette since usually we have a non linear distribution of percentages and very near gray tones are hard to take apart. Final part of the palette is gradient from yellow to red. The red part is hardly reached because of usual distribution of latencies, but shows up mainly when latencies are very high because of the logarithmic scale, this is coherent to what people expect: red = bad.
* redis-cli --stat: show LOAD when loading.antirez2015-02-111-0/+4
|
* redis-cli --lru-test implemented (cache workload simulator).antirez2015-02-091-0/+102
|
* redis-cli: interactive reconnection for latency modes.antirez2015-02-081-9/+13
| | | | | | | | | | | | --stat mode already used to reconnect automatically if the server is no longer available. This is useful since this is an interactive mode used for debugging, however the same applies to --latency and --latency-dist modes, so now both use the reconnecting command execution as well. The reconnection code was modified to use basic VT100 escape sequences in order to play better with different kinds of output on the screen when the reconnection happens, and to hide the reconnection attempt output when finally the reconnection happens.
* redis-cli --latecy-dist reverted to gray scale.antirez2015-02-081-8/+10
| | | | | | So far not able to find a color palette within the 256 colors which is not confusing. However I believe it is a possible task, so will try better later.
View Lorry Controller Status