Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
144d479b
Commit
144d479b
authored
May 28, 2009
by
antirez
Browse files
minor fix for Solaris boxes
parent
3fd78bcd
Changes
2
Hide whitespace changes
Inline
Side-by-side
pqsort.c
View file @
144d479b
...
@@ -37,6 +37,8 @@
...
@@ -37,6 +37,8 @@
* SUCH DAMAGE.
* SUCH DAMAGE.
*/
*/
#define __P(protos) protos
#include <sys/cdefs.h>
#include <sys/cdefs.h>
#if defined(LIBC_SCCS) && !defined(lint)
#if defined(LIBC_SCCS) && !defined(lint)
#if 0
#if 0
...
...
redis.conf
View file @
144d479b
...
@@ -97,6 +97,13 @@ databases 16
...
@@ -97,6 +97,13 @@ databases 16
# If all this fails, Redis will start to reply with errors to commands
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
# maxmemory <bytes>
# maxmemory <bytes>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment