1. 06 Oct, 2014 2 commits
  2. 26 Aug, 2014 1 commit
  3. 19 Aug, 2013 1 commit
  4. 28 Jan, 2013 1 commit
  5. 19 Nov, 2012 1 commit
  6. 08 Nov, 2012 1 commit
  7. 13 Aug, 2012 2 commits
  8. 18 Jul, 2012 1 commit
    • antirez's avatar
      Don't assume that "char" is signed. · b62bdf1c
      antirez authored
      For the C standard char can be either signed or unsigned, it's up to the
      compiler, but Redis assumed that it was signed in a few places.
      
      The practical effect of this patch is that now Redis 2.6 will run
      correctly in every system where char is unsigned, notably the RaspBerry
      PI and other ARM systems with GCC.
      
      Thanks to Georgi Marinov (@eesn on twitter) that reported the problem
      and allowed me to use his RaspBerry via SSH to trace and fix the issue!
      b62bdf1c
  9. 14 Jun, 2012 1 commit
    • antirez's avatar
      ziplistFind(): don't assume that entries are comparable by encoding. · ba779119
      antirez authored
      Because Redis 2.6 introduced new integer encodings it is no longer true
      that if two entries have a different encoding they are not equal.
      
      An old ziplist can be loaded from an RDB file generated with Redis 2.4,
      in this case for instance a small unsigned integers is encoded with a
      16 bit encoding, while in Redis 2.6 a more specific 8 bit encoding
      format is used.
      
      Because of this bug hashes ended with duplicated values or fields lookup
      failed, causing many bad behaviors.
      This in turn caused a crash while converting the ziplist encoded hash into
      a real hash table because an assertion was raised on duplicated elements.
      
      This commit fixes issue #547.
      
      Many thanks to Pinterest's Marty Weiner and colleagues for discovering
      the problem and helping us in the debugging process.
      ba779119
  10. 06 May, 2012 1 commit
    • Pieter Noordhuis's avatar
      Compare integers in ziplist regardless of encoding · bf219416
      Pieter Noordhuis authored
      Because of the introduction of new integer encoding types for ziplists
      in the 2.6 tree, the same integer value may have a different encoding in
      different versions of the ziplist implementation. This means that the
      encoding can NOT be used as a fast path in comparing integers.
      bf219416
  11. 24 Apr, 2012 4 commits
  12. 23 Mar, 2012 1 commit
  13. 14 Feb, 2012 1 commit
  14. 09 Feb, 2012 3 commits
  15. 08 Feb, 2012 2 commits
  16. 04 Jan, 2012 1 commit
    • Pieter Noordhuis's avatar
      Implements ziplistFind · fe458402
      Pieter Noordhuis authored
      To improve the performance of the ziplist implementation, some
      functions have been converted to macros to avoid unnecessary stack
      movement and duplicate variable assignments.
      fe458402
  17. 23 Oct, 2011 1 commit
  18. 05 May, 2011 2 commits
  19. 14 Mar, 2011 1 commit
  20. 09 Mar, 2011 1 commit
  21. 28 Feb, 2011 1 commit
  22. 23 Dec, 2010 1 commit
  23. 07 Dec, 2010 1 commit
  24. 02 Nov, 2010 1 commit
  25. 14 Oct, 2010 1 commit
  26. 23 Sep, 2010 1 commit
  27. 06 Sep, 2010 2 commits
  28. 13 Aug, 2010 1 commit
  29. 27 Jul, 2010 1 commit
  30. 01 Jul, 2010 1 commit