Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
01e95705
Commit
01e95705
authored
Feb 07, 2012
by
antirez
Browse files
Fixes to 2.6 release notes file
parent
c2513ecb
Changes
1
Hide whitespace changes
Inline
Side-by-side
00-RELEASENOTES
View file @
01e95705
...
@@ -3,18 +3,15 @@ Redis 2.6 release notes
...
@@ -3,18 +3,15 @@ Redis 2.6 release notes
Migrating from 2.4 to 2.6
Migrating from 2.4 to 2.6
=========================
=========================
Redis 2.4 is mostly a strict subset of 2.6.
Redis 2.4 is mostly a strict subset of 2.6. However there are a few things
The only thing you should be aware is that you can't use .rdb and AOF files
that you should be aware of:
generated with 2.4 into a 2.2 instance.
2.4 slaves can be attached to 2.2 masters, but not the contrary, and only for
* You can't use .rdb and AOF files generated with 2.6 into a 2.4 instance.
the time needed to perform the version upgrade.
* 2.4 slaves can be attached to 2.6 masters, but not the contrary, and only
for the time needed to perform the version upgrade.
From the point of view of the API Redis 2.4 only adds new commands
There are also a few API differences, that are unlikely to cause problems,
(other commands now accepts a variable number of arguments) so you don't need
but it is better to keep them in mind:
to modify your program in order to use Redis 2.4.
However there are a few semantical differences that you should be aware of:
* SORT now will refuse to sort in numerical mode elements that can't be parsed
* SORT now will refuse to sort in numerical mode elements that can't be parsed
as numbers.
as numbers.
...
@@ -22,7 +19,8 @@ However there are a few semantical differences that you should be aware of:
...
@@ -22,7 +19,8 @@ However there are a few semantical differences that you should be aware of:
break code that was not conceived exploting the previous resolution error
break code that was not conceived exploting the previous resolution error
in some way.)
in some way.)
* INFO output is a bit different now, and contains empty lines and comments
* INFO output is a bit different now, and contains empty lines and comments
starting with '#'.
starting with '#'. All the major clients should be already fixed to work
with the new INFO format.
---------
---------
CHANGELOG
CHANGELOG
...
...
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