X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/7c5d96d98e6cc2a0e7ea5ea30e3ca4772a84b3cb..473f3090f2574e8a2f5db5f18ab7387040829108:/00-RELEASENOTES diff --git a/00-RELEASENOTES b/00-RELEASENOTES index d4364bc7..a5ff7f2d 100644 --- a/00-RELEASENOTES +++ b/00-RELEASENOTES @@ -1,36 +1,34 @@ Redis 2.6 release notes +======================= -Migrating from 2.4 to 2.6 -========================= +** IMPORTANT ** Check the 'Migrating from 2.4 to 2.6' section at the end of + this file for information about what changed between 2.4 and + 2.6 and how this may affect your application. -Redis 2.4 is mostly a strict subset of 2.6. However there are a few things -that you should be aware of: +What's new in Redis 2.5.9 (aka 2.6 Release Candidate 3) +======================================================= -* You can't use .rdb and AOF files generated with 2.6 into a 2.4 instance. -* 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. +UPGRADE URGENCY: critical, upgrade ASAP. -There are also a few API differences, that are unlikely to cause problems, -but it is better to keep them in mind: +* [BUGFIX] Fix for issue #500 (https://github.com/antirez/redis/pull/500). + Redis 2.6-RC1 and RC2 may corrupt ziplist-encoded sorted sets + produced by Redis 2.4.x. +* [BUGFIX] Fixed several bugs in init.d script. +* [BUGFIX] syncio.c functions modified for speed and correctness. On osx + (and possibly other BSD-based systems) the slave would block on + replication to send the SYNC command when the master was not + available. This is fixed now, but was not affecting Linux installs. +* Now when slave-serve-stale-data is set to yes and the master is down, instead + of reporting a generic error Redis replies with -MASTERDOWN. -* SORT now will refuse to sort in numerical mode elements that can't be parsed - as numbers. -* EXPIREs now all have millisecond resolution (but this is very unlikely to - break code that was not conceived exploting the previous resolution error - in some way.) -* INFO output is a bit different now, and contains empty lines and comments - starting with '#'. All the major clients should be already fixed to work - with the new INFO format. - -Also the following redis.conf and CONFIG GET / SET parameters changed name: +What's new in Redis 2.5.8 (aka 2.6 Release Candidate 2) +======================================================= - * hash-max-zipmap-entries, now replaced by hash-max-ziplist-entries - * hash-max-zipmap-value, now replaced by hash-max-ziplist-value - * glueoutputbuf was no completely removed as it does not make sense +UPGRADE URGENCY: high for all the users of the KEYS command, otherwise low. ---------- -CHANGELOG ---------- +* [BUGFIX] Fix for KEYS command: if the DB contains keys with expires the KEYS + command may return the wrong output, having duplicated or missing + keys. See issue #487 and #488 on github for details. What's new in Redis 2.5.7 (aka 2.6 Release Candidate 1) ======================================================= @@ -53,6 +51,7 @@ An overview of new features and changes in Redis 2.6.x precision (PEXPIRE, PTTL, ...). * Better memory usage for "small" lists, ziplists and hashes when fields or values contain small integers. +* Read only slaves. * Clients max output buffer soft and hard limits. You can specifiy different limits for different classes of clients (normal,pubsub,slave). * AOF is now able to rewrite aggregate data types using variadic commands, @@ -86,6 +85,46 @@ An overview of new features and changes in Redis 2.6.x * Better support for big endian and *BSD systems. * Build system improved. +Migrating from 2.4 to 2.6 +========================= + +Redis 2.4 is mostly a strict subset of 2.6. However there are a few things +that you should be aware of: + +* You can't use .rdb and AOF files generated with 2.6 into a 2.4 instance. +* 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. + +There are also a few API differences, that are unlikely to cause problems, +but it is better to keep them in mind: + +* SORT now will refuse to sort in numerical mode elements that can't be parsed + as numbers. +* EXPIREs now all have millisecond resolution (but this is very unlikely to + break code that was not conceived exploting the previous resolution error + in some way.) +* INFO output is a bit different now, and contains empty lines and comments + starting with '#'. All the major clients should be already fixed to work + with the new INFO format. +* Slaves are only read-only by default (but you can change this easily + setting the "slave-read-only" configuration option to "no" editing your + redis.conf or using CONFIG SET. + +The following INFO fields were renamed for consistency: + + changes_since_last_save -> rdb_changes_since_last_save + bgsave_in_progress -> rdb_bgsave_in_progress + last_save_time -> rdb_last_save_time + last_bgsave_status -> rdb_last_bgsave_status + bgrewriteaof_in_progress -> aof_rewrite_in_progress + bgrewriteaof_scheduled -> aof_rewrite_scheduled + +The following redis.conf and CONFIG GET / SET parameters changed: + + * hash-max-zipmap-entries, now replaced by hash-max-ziplist-entries + * hash-max-zipmap-value, now replaced by hash-max-ziplist-value + * glueoutputbuf option was now completely removed (was deprecated) + -------------------------------------------------------------------------------- Credits: Where not specified the implementation and design are done by